-
Notifications
You must be signed in to change notification settings - Fork 39
Closed
Milestone
Description
- QUADS version (
rpm -qa | grep quadsand/orquads --version): QUADS version 2.1.6 bowie - Python version: Python 3.12.7
- Operating System: F40
Describe the bug
Running: quads --host hostname --ls-schedule doesn't always show schedules in chronological order, e.g.
# quads --host $(quads --cloud-only --cloud cloud40 | tail -1) --ls-schedule
Default cloud: cloud01
Current cloud: cloud40
Current schedule: 3052
2242| start=2024-08-04T22:00, end=2024-09-01T22:00, cloud=cloud42
2458| start=2024-09-04T11:35, end=2024-11-03T22:00, cloud=cloud43
3052| start=2024-11-05T16:00, end=2025-04-06T22:00, cloud=cloud40
3044| start=2024-11-05T13:50, end=2024-11-05T15:24, cloud=cloud13
Notice that the schedule ID 3044 is lower than schedule id 3052, and even appears chronologically before the current (cloud40) schedule, but for some reason is printed to the screen in the output after the latest schedule.
Metadata
Metadata
Assignees
Type
Projects
Status
Done