I'm running these commands to look at the resources consumed by running jobs: > FORMAT_ACTIVE="jobid:8,userid:14,timelimit:14,timeused:12,partition:13" > squeue -t R -a -S u -O $FORMAT_ACTIVE # Sorts by user, to show the hogs. > squeue -t R -a -S M -O $FORMAT_ACTIVE # Sorts by time consumed, just for illustration. > squeue -t R -a -S P -O $FORMAT_ACTIVE # Sorts by partition name, showing degree of saturation. The third form doesn't do what it's supposed to, though, it's sorting by time (the same as "-S M") instead of partition name: JOBID UID TIME_LIMIT TIME PARTITION 471890 20016 2:00:00 0:38 interactive 471834 10007 2:00:00 3:35 backfill 471868 10030 30:00 3:36 ci-manual 471822 10030 1:40:00 14:54 ci-manual 471711 10062 2:00:00 32:31 backfill 471808 10007 2:00:00 46:29 admin 471800 10023 4:00:00 57:08 admin 471676 10062 2:00:00 1:11:26 backfill 471766 10062 2:00:00 1:16:10 backfill 471765 10062 2:00:00 1:16:40 backfill 471767 20022 2:00:00 1:16:40 interactive 471759 10062 2:00:00 1:23:04 backfill
Hey Luke, I may have already found a solution for this one. Let me run some more tests and max sure this fix works. ~Colby
fixed in https://github.com/SchedMD/slurm/commit/4ab0960cc2ffeb78431e154620890cfb7147ca5f ~colby
I ran into the same problem trying to sort by JobID: squeue -h -S J -j846819,847010,854468,861880,862137,862139,863129,863148,863234 -O jobid:8 squeue -h -S +J -j846819,847010,854468,861880,862137,862139,863129,863148,863234 -O jobid:8 squeue -h -S -J -j846819,847010,854468,861880,862137,862139,863129,863148,863234 -O jobid:8 where the list isn't monotonic up or down. Also, I would have expected this form squeue -h -t PD -j846819,847010,854468,861880,862137,862139,863129,863148,863234 -O jobid:8 to print the information in the same order that I specified in the -j parameter, but it doesn't come out that way.
Hey Carl, Could you create a new bug. You can just copy paste what you put as your comment in here. ~Colby
Ok opened this bug https://bugs.schedmd.com/show_bug.cgi?id=10164 I suspect, though, that the -S problem stems from the same cause as this bug.
Fix confirmed in 20.02.6, thanks.