implement crab -resubmit bad

[ericvaandering]

Original Savannah ticket 99942 reported by belforte on Mon Jan 21 04:19:51 2013.

Hi, I'd like to propose you a new feature for crab2, that allows to resubmit the set of failed jobs without having to copy-paste by hand the list(s) of failed jobs from -status output.

The use case should be obvious: it is particularly important in case multicrab is used. In that case it is not possible to resubmit via multicrab, since each task need its own list of failed job.

The syntax could be simply

crab -resubmit bad

(similar to crab -resubmit all )

I have the modification in the code ready in 284 and I'm using it w/o problems (crab.py, Resubmitter.py and ResubmitterServer.py)

The implementation is such that the following jobs are resubmitted:

in status ['KillSuccess','SubFailed','Aborted']

in status ['Cleared'] if the job or wrapper exit code is not 0.

The set can be expanded easily.

ADD: ['Cancelled'] to be added exit code 60308 to be skipped

[ericvaandering]

Comment by slacapra on Thu Jan 17 10:25:20 2013

Committed into CVS

Modified Files: crab.py Resubmitter.py ResubmitterServer.py Log Message: implement -resubmit bad as per task #39244

[ericvaandering]

Comment by belforte on Mon Jan 21 04:19:51 2013

This item has been reassigned from the project CRAB task tracker to your tracker.

The original report is still available at task #39244

Following are the information included in the original report:

• [field #0] Item ID: 39244
• [field #1] Group ID: 265
• [field #2] Open/Closed: Closed
• [field #3] Severity: 3 - Normal
• [field #4] Privacy: Public
• [field #9] Category: crab client
• [field #10] Submitted by: slacapra
• [field #11] Assigned to: slacapra
• [field #12] Submitted on: 2013-01-17 15:29
• [field #13] Summary: implement crab -resubmit bad
• [field #14] Original Submission: Hi, I d like to propose you a new feature for crab2, that allows to resubmit the set of failed jobs without having to copy-paste by hand the list(s) of failed jobs from -status output.

The use case should be obvious: it is particularly important in case multicrab is used. In that case it is not possible to resubmit via multicrab, since each task need its own list of failed job.

The syntax could be simply

crab -resubmit bad

(similar to crab -resubmit all )

I have the modification in the code ready in 284 and I m using it w/o problems (crab.py, Resubmitter.py and ResubmitterServer.py)

The implementation is such that the following jobs are resubmitted:

in status [ KillSuccess , SubFailed , Aborted ]

in status [ Cleared ] if the job or wrapper exit code is not 0.

The set can be expanded easily.

ADD: [ Cancelled ] to be added exit code 60308 to be skipped

• [field #15] Closed on: 2013-01-17 16:25
• [field #16] Item Group: None
• [field #17] Status: Done
• [field #18] Component Version: None
• [field #19] Operating System: None
• [field #20] Reproducibility: None
• [field #21] Size (loc): None
• [field #22] Fixed Release: None
• [field #23] Planned Release: None
• [field #24] Effort: 0.00
• [field #28] Priority: 3 - Low
• [field #29] Should Start On: 2013-01-17 00:00
• [field #30] Should be Finished on: 2013-01-17 00:00
• [field #31] Percent Complete: 0%
• [field #33] Release: None
• [field #34] Release: 285
• [field #58] Custom Select Box #1: None
• [field #59] Custom Select Box #2: None
• [field #60] Custom Select Box #3: None
• [field #61] Custom Select Box #4: None
• [field #62] Custom Select Box #5: None
• [field #63] Custom Select Box #6: None
• [field #64] Custom Select Box #7: None
• [field #65] Custom Select Box #8: None
• [field #66] Custom Select Box #9: None
• [field #67] Custom Select Box #10: None

[ericvaandering]

Closed by belforte on Tue Jan 29 06:42:40 2013

[ericvaandering]

Comment by belforte on Tue Jan 29 06:42:40 2013

released in CRAB_2_8_5