Re: [slurm-users] squeue: compact pending job-array in one partition, but not in other

2021-02-24 Thread Thomas M. Payerle
I believe this behavior is intended as various properties of the jobs that were requeued no longer match the properties of the rest of the job array. It might not show on the minimal output you are displaying, but I suspect the jobs were requeued at different times and so the priorities of the jobs

Re: [slurm-users] squeue: compact pending job-array in one partition, but not in other

2021-02-23 Thread Loris Bennett
Hi Jeffrey, Yes, those jobs (and elements of other array which were also listed one per line) had indeed been preempted and requeued. So is this behaviour intended/documented or is it a bug? Cheers, Loris Jeffrey T Frey writes: > Did those four jobs > > >6577272_21 scavenger PD

Re: [slurm-users] squeue: compact pending job-array in one partition, but not in other

2021-02-23 Thread Jeffrey T Frey
Did those four jobs 6577272_21 scavenger PD 0:00 1 (Priority) 6577272_22 scavenger PD 0:00 1 (Priority) 6577272_23 scavenger PD 0:00 1 (Priority) 6577272_28 scavenger PD 0:00 1 (Priority) run before and get requeued? Seems

[slurm-users] squeue: compact pending job-array in one partition, but not in other

2021-02-23 Thread Loris Bennett
Hi, Does anyone have an idea why pending elements of an array job in one partition should be displayed compactly by 'squeue' but those of another in a different partition are displayed one element per line? Please see below (compact display in 'main', one element per line in 'scavenger'). This is