Bug #22132
closed
Adjust scheduling status display based on feedback
Added by Peter Amstutz 2 months ago. Updated about 2 months ago.
Description
Files
| scheduling-status-log.png (150 KB) scheduling-status-log.png | Peter Amstutz, 09/18/2024 03:10 PM | ||
| scheduling-status-float-right.png (147 KB) scheduling-status-float-right.png | Peter Amstutz, 09/18/2024 03:10 PM | ||
| scheduling-status-detail.png (152 KB) scheduling-status-detail.png | Peter Amstutz, 09/18/2024 03:10 PM | ||
| scheduling-status-top.png (147 KB) scheduling-status-top.png | Peter Amstutz, 09/18/2024 03:10 PM |
Related issues
Updated by Peter Amstutz 2 months ago
- Related to Feature #21297: use container_status API to display scheduling feedback on cloud added
Updated by Peter Amstutz 2 months ago
- Subject changed from Adjust container status display based on feedback to Adjust scheduling status display based on feedback
Updated by Peter Amstutz 2 months ago
- Description updated (diff)
- File scheduling-status-detail.png scheduling-status-detail.png added
- File scheduling-status-top.png scheduling-status-top.png added
- File scheduling-status-float-right.png scheduling-status-float-right.png added
- File scheduling-status-log.png scheduling-status-log.png added
Updated by Peter Amstutz 2 months ago
Prefer to display as log with timestamp
Each time it re-queries, add it to the end.
Updated by Peter Amstutz about 2 months ago
- Status changed from New to In Progress
Updated by Peter Amstutz about 2 months ago
22132-scheduling-status-log @ f4013d381074bfcc1856597dfdb891fa1d0569e9
Updated by Peter Amstutz about 2 months ago
- Target version changed from Development 2024-09-25 sprint to Development 2024-10-09 sprint
Updated by Peter Amstutz about 2 months ago
22132-scheduling-status-log @ ca45a8fe46f4f8520438d01bb7ae5ff28a7e73bb
Updated by Peter Amstutz about 2 months ago
22132-scheduling-status-messages @ 8668fd5770e7512857821007fba8babf90117ffd
Wordsmithed the scheduling status messages to hopefully be more useful to the end user.
Updated by Tom Clegg about 2 months ago
Peter Amstutz wrote in #note-9:
22132-scheduling-status-log @ ca45a8fe46f4f8520438d01bb7ae5ff28a7e73bb
(I'm not reviewing this branch but) it looks like the timestamp regexp is trying to make fractional seconds optional, but didn't make the last "." optional. Maybe should be something like this?
- ... :[0-9]{2}\.[0-9]{0,}Z
+ ... :[0-9]{2}(\.[0-9]{1,9})?Z
Updated by Tom Clegg about 2 months ago
Peter Amstutz wrote in #note-10:
22132-scheduling-status-messages @ 8668fd5770e7512857821007fba8babf90117ffd
I think we should update the examples in source:doc/api/dispatch.html.textile.liquid so the capitalization/punctuation matches the new complete-sentence style.
Wording nitpicks:- "Cluster is at capacity for all the eligible instance types" would be better without "the".
- "Waiting in container queue" would be better without "container".
Rest LGTM, thanks.
Updated by Lisa Knox about 2 months ago
Wordsmithed the scheduling status messages to hopefully be more useful to the end user.
Messaging to the user is much more readable, while being both thorough and concise.
Updated by Lisa Knox about 2 months ago
Peter Amstutz wrote in #note-9:
22132-scheduling-status-log @ ca45a8fe46f4f8520438d01bb7ae5ff28a7e73bb
pending tests, this lgtm
Updated by Peter Amstutz about 2 months ago
- Status changed from In Progress to Resolved