improve readability of -status

[ericvaandering]

Original Savannah ticket 100080 reported by belforte on Fri Jan 25 14:21:46 2013.

For large task, the readability of -status is low: the printout is typically too long and the important information are not immediately visible.

I propose two improvement:

1) the possibility to switch off the printout of the status of each job

2) the possibility to color the output, it the output stream allows for it.

Both improvement are quite helpful when multicrab is used.

The proposed syntax is

crab -status short (for 1) crab -status color (for 2) crab -status short,color (for 1+2)

For 2, only the summary will be colored. In general, green is the color for good jobs (done, exit =0 etc), Red for bad ones (abort, exit>0, etc), yellow for Created, Blue for job ended in "strange" status. Job which are on the grid are not colored.

An example is attached.

[ericvaandering]

Comment by slacapra on Fri Jan 25 05:09:11 2013

commit into CVS an implementation.

crab.py crab_util.py Status.py

Stefano

[ericvaandering]

Comment by belforte on Fri Jan 25 14:21:46 2013

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

The original report is still available at task #39391

Following are the information included in the original report:

• [field #0] Item ID: 39391
• [field #1] Group ID: 265
• [field #2] Open/Closed: Open
• [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-25 11:04
• [field #13] Summary: improve readability of -status
• [field #14] Original Submission: For large task, the readability of -status is low: the printout is typically too long and the important information are not immediately visible.

I propose two improvement:

1) the possibility to switch off the printout of the status of each job

2) the possibility to color the output, it the output stream allows for it.

Both improvement are quite helpful when multicrab is used.

The proposed syntax is

crab -status short (for 1) crab -status color (for 2) crab -status short,color (for 1+2)

For 2, only the summary will be colored. In general, green is the color for good jobs (done, exit =0 etc), Red for bad ones (abort, exit>0, etc), yellow for Created, Blue for job ended in "strange" status. Job which are on the grid are not colored.

An example is attached.

• [field #16] Item Group: None
• [field #17] Status: None
• [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-25 00:00
• [field #30] Should be Finished on: 2013-01-31 00:00
• [field #31] Percent Complete: 80%
• [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]

Comment by belforte on Fri Jan 25 14:25:03 2013

commits imported in latest tag CRAB_2_8_5_pre5 those are: crab.py crab_util.py Status.py crab_help.py

[ericvaandering]

Comment by belforte on Fri Jan 25 14:56:11 2013

but I disabled coloring of standard header and trailer of crab commands. To keep same look as before. If you like to have them Stefano, I suggest to use an option in crab.cfg

[ericvaandering]

Comment by belforte on Tue Jan 29 06:38:30 2013

released in CRAB_2_8_5

[ericvaandering]

Closed by belforte on Tue Jan 29 06:38:30 2013