1. 13 Feb, 2014 3 commits
  2. 12 Feb, 2014 1 commit
  3. 11 Feb, 2014 1 commit
    • Klaus Aehlig's avatar
      Consider job-IDs queried for twice only once · fb8d8645
      Klaus Aehlig authored
      As reading jobs from disk is an expensive operation, when querying
      for jobs, we optimize by considering which values the job-id is asked
      for in the filter. As any reasonable person would not add the same
      clause twice in an Or-clause, the implicit assumption was that the
      job ids obtained by inspecting the filter would be unique; hence the
      information for those jobs could be returned directly.
      
      That all did hold true and everyone was happy till with commit 13ef1fa5
      
      
      a query for a single job suddenly returned the job twice violating
      WaitForJobChange's expectation. Fix this by taking the nub of the
      jids asked for in the filter.
      Signed-off-by: default avatarKlaus Aehlig <aehlig@google.com>
      Reviewed-by: default avatarHrvoje Ribicic <riba@google.com>
      fb8d8645
  4. 10 Feb, 2014 1 commit
  5. 07 Feb, 2014 9 commits
  6. 06 Feb, 2014 14 commits
  7. 04 Feb, 2014 7 commits
  8. 30 Jan, 2014 4 commits