Bug #3442

Can re-use job where the job is readable but the output collection isn't.

Added by Peter Amstutz almost 6 years ago. Updated almost 6 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
API
Target version:
Start date:
08/01/2014
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
Story points:
0.5

Subtasks

Task #3449: Review 3442-no-reuse-job-when-output-unreadableResolvedTim Pierce

Associated revisions

Revision d579e706
Added by Peter Amstutz almost 6 years ago

Merge branch 'origin-3442-no-reuse-job-when-output-unreadable' refs #3442

History

#1 Updated by Peter Amstutz almost 6 years ago

  • Target version set to 2014-08-06 Sprint

#2 Updated by Peter Amstutz almost 6 years ago

  • Category set to API
  • Assigned To set to Peter Amstutz

#3 Updated by Peter Amstutz almost 6 years ago

  • Status changed from New to In Progress

#4 Updated by Peter Amstutz almost 6 years ago

  • Story points set to 0.5

#5 Updated by Tim Pierce almost 6 years ago

Review at ee91e2e:

Minor comments only:

  • services/api/test/fixtures/links.yml
    • foo_repo_readable_by_job_reader: comment should say "foo_repo" instead of "previous_job_run" :-)
    • Maybe also name it "job_reader_can_read_foo_repo" for parallelism with the previous fixture

Otherwise LGTM, thanks.

#6 Updated by Peter Amstutz almost 6 years ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF