fix: use correct shorthand for 'Running' in the scheduler#141
Merged
AlexJones0 merged 1 commit intolowRISC:masterfrom Apr 2, 2026
Merged
Conversation
When the 'DISPATCHED' status name was changed to 'RUNNING', I remembered to replace the status header, but forgot to replace the hardcoded shorthand in the status bar messages in the core scheduler logic. This will be addressed by the new async status printers, but should also be fixed in the scheduler in the meantime to prevent confusion. Signed-off-by: Alex Jones <alex.jones@lowrisc.org>
jwnrt
approved these changes
Apr 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix a minor bug introduced by #129 (specifically 6225898), where 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.
This will be addressed by the new async status printers (#137), but should still be fixed in the scheduler in the meantime to prevent any confusion.
Closes #140.