- 10 May, 2013 12 commits
-
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
to be running in the calling program.
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Rod Schultz authored
-
David Bigagli authored
-
- 09 May, 2013 1 commit
-
-
David Bigagli authored
-
- 08 May, 2013 4 commits
-
-
David Bigagli authored
-
David Bigagli authored
-
jette authored
-
Danny Auble authored
the node tab and we didn't notice.
-
- 07 May, 2013 4 commits
-
-
David Bigagli authored
-
David Bigagli authored
which reads the array boundary.
-
David Bigagli authored
-
David Bigagli authored
the daemon to core dump.
-
- 05 May, 2013 1 commit
-
-
Hongjia Cao authored
-
- 04 May, 2013 2 commits
-
-
Morris Jette authored
-
Morris Jette authored
Response to bug 274
-
- 03 May, 2013 9 commits
-
-
Morris Jette authored
If a user requests multiple counts of a specific GRES type (e.g. "--gres=gpu:2") and those GRES are associated with specific CPUs, the job submit could fail without this change.
-
Morris Jette authored
-
David Bigagli authored
-
David Bigagli authored
-
jette authored
-
David Bigagli authored
-
David Bigagli authored
-
Morris Jette authored
Conflicts: testsuite/expect/test1.90
-
jette authored
Make test work if current working directory not in the search path Check for appropriate task rank on POE based systems Disable the entire test on POE systems
-
- 02 May, 2013 7 commits
-
-
Morris Jette authored
The option "interval" was the original parameter, but has not been documented for a year or more.
-
Morris Jette authored
-
jette authored
Without this change pmdv12 was bound to one CPU and could not use all of the resources allocated to the job step for the tasks that it launches
-
jette authored
This only changes behaviour when the --ntasks option is not used, but the --cpus-per-task option is use
-
jette authored
-
jette authored
-
Danny Auble authored
-