-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/03/13 08:06, Moe Jette wrote:
> -- BGQ - More robust checking for correct node, task, and > ntasks-per-node options in srun, and push that logic to salloc and > sbatch. This fix just broke our users workflow as their legitimate jobs (32 or 64 tasks per node) are now rejected by srun. They're going to work to fix up their workflow but they were not impressed with having to do so for (as far as they are concerned) no good reason, and we weren't expecting this sort of behaviour change in a minor point release. Is this something we could modify the behaviour of via the SLURM Job Submit Plugin API? cheers, Chris - -- Christopher Samuel Senior Systems Administrator VLSCI - Victorian Life Sciences Computation Initiative Email: [email protected] Phone: +61 (0)3 903 55545 http://lists.schedmd.com/cgi-bin/dada/mail.cgi/r/slurmdev/883446755620/ http://lists.schedmd.com/cgi-bin/dada/mail.cgi/r/slurmdev/619754772499/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://lists.schedmd.com/cgi-bin/dada/mail.cgi/r/slurmdev/841295470537/ iEYEARECAAYFAlE9LKEACgkQO2KABBYQAh+dyACfVghkeGXnzZo/A6j4hR196h5V BEQAn0vMhuiqktwSLS1ghlVcVZjR5z6h =T8C4 -----END PGP SIGNATURE-----
