Skip to content

Running/Dispatched status name shorthand mismatch in the status printer #140

@AlexJones0

Description

@AlexJones0

See the example output:

          [   legend    ]: [Q: queued, R: running, P: passed, F: failed, K: killed, T: total]                                                                                                                                                                                                                                                   
00:04:58  [    build    ]: [Q: 00, D: 00, P: 00, F: 02, K: 93, T: 95] 100%                                                                                                                                                                                                                                                                      
00:04:58  [     run     ]: [Q: 00, D: 00, P: 00, F: 00, K: 1574, T: 1574] 100%                                                                                                                                                                                                                                                                  
00:04:58  [  cov_merge  ]: [Q: 00, D: 00, P: 00, F: 00, K: 47, T: 47] 100%                                                                                                                                                                                                                                                                      
00:04:58  [ cov_report  ]: [Q: 00, D: 00, P: 00, F: 00, K: 47, T: 47] 100%

R: running is used in the legend but D: is used as the shorthand in the status bar messages.

In #129, the "Dispatched" job status was renamed to "Running". When I made this change, I remembered to replace the status header, but forgot to replace the hard-coded shorthand in the status bar messages in the core scheduler logic, because I later rewrote the scheduler / status bars to automatically derive these messages from the shorthand, and did not realize this issue would occur when merging the changes in stages.

While this logic will be addressed by the new async status printers, it should also be fixed in the scheduler in the meantime to prevent confusion.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions