Are you saying without the option turned on you get different behaviour than before? That seems very strange. Without the option turned on there shouldn't be any code change. This is the result I would expect of the option was turned on.

On October 11, 2014 9:48:33 AM PDT, bugs@schedmd.com wrote:

Comment # 4 on bug 1159 from 
Running " salloc " with no options on 2 different systems with the same CLE and
slurm. see " apstat -r" output.

1.) without patch: salloc with no option allocates 8 tasks/node  

nina@santis01:~ $ salloc
salloc: Granted job allocation 64
salloc: Waiting for resource configuration
salloc: Nodes nid00014 are ready for job
nina@santis01:~ $ apstat -r
  ResId   ApId From     Arch PEs N d Memory State
  39603 140829 batch:64   XT   8 8 1      1 NID list,conf
nina@santis01:~ $ aprun -n2 hostname | wc -l
3

2.) with patch - salloc with no option only give 1 task/node and therefore
aprun -2 fails:

nina@brisi01:~ $ salloc
salloc: Granted job allocation 1150
salloc: Waiting for resource configuration
salloc: Nodes nid00057 are ready for job
nina@brisi01:~ $ apstat -r
  ResId   ApId From       Arch PEs N d Memory State
  38193 135232 batch:1150   XT   1 1 1  65536 NID list,conf
nina@brisi01:~ $ aprun -n2 hostname | wc -l
apsched: claim exceeds reservation's node-count
0

Can you pass on to schedMD?
You are receiving this mail because: