This bug was introduced in 17.02.2 with commit
fec995e0cd0870a77b277c7608876abc541c28d6 Fix gres output of a job if it is
updated while pending to be displayed
correctly with Slurm tools. What this does is replace the incoming string with
the gres actually chosen. Continuation of last commit. Bug 3521
When name:type:cnt is requested, type and cnt are being stripped stripped in
_get_gres_req_cnt with
if (type && ((cnt == -1) || (type != num))) {
type[0] = '\0';
if (num && type != num)
num[0] = '\0';
type++;
*type_out = xstrdup(type);
Can someone familiar with the gres code explain what is/should be happening in
get_gres_req_cnt?
thanks,
-brian
On 07/05/2017 08:15 AM, Shawn Bobbin wrote:
Hi,
One of our users reported a change in behavior in 17.02-2 with the gres output
in the `squeue` command. Specifically it doesn’t show details about the gres
resources being used. For example:
On 15.08:
-bash-4.2$ sbatch --gres=gpu:1 test.sh
Submitted batch job 1124
-bash-4.2$ sbatch --gres=gpu:m40:1 test.sh
Submitted batch job 1125
-bash-4.2$ squeue -o "%i %b"
JOBID GRES
1124 gpu:1
1125 gpu:m40:1
And on 17.02:
-bash-4.2$ sbatch --partition=scavenger --qos=scavenger --gres=gpu:1 test.sh
Submitted batch job 20094
-bash-4.2$ sbatch --partition=scavenger --qos=scavenger --gres=gpu:p6000:1
test.sh
Submitted batch job 20095
-bash-4.2$ squeue -o "%i %b" | grep -e '20094' -e '20095'
20095 gpu
20094 gpu:1
In 15.08 squeue lists whats GPUs are being consumed, and in 17.02 it does not.
We wanted to check in and see if this was an expected change in behavior or a
bug. I briefly searched through the changelog, and didn’t see any mention.
Thanks!
—Shawn
