Project

General

Profile

Bug #566

Checklbns rerun gives bad status to good runs

Added by Marc Mengel over 9 years ago. Updated over 9 years ago.

Status:
Accepted
Priority:
Normal
Assignee:
Start date:
07/08/2010
Due date:
% Done:

90%

Estimated time:
0.50 h
Duration:

Description

The code can get confused and try to run checklbns again, after it's already been run and the files
moved to good_lbns. We need to only run checklbns on datasets that are actually in the output
directory.

History

#1 Updated by Marc Mengel over 9 years ago

Now we compute the intersection of the list of runs in the output area and the jobs that look like we should check their LBNS, and that's what we actually check for LBNS. See r4, r6 and r7

#2 Updated by Marc Mengel over 9 years ago

  • % Done changed from 10 to 90


Also available in: Atom PDF