- 18 Jul, 2017 6 commits
-
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
Fix for debugger setup bug introduced in commit f1110568
-
Morris Jette authored
-
- 17 Jul, 2017 5 commits
-
-
Morris Jette authored
Avoid interleaving labels and output from various components of a pack job
-
Morris Jette authored
This allocates an array to the proper size (based upon all tasks to be launched). Work still needed to populate the data structure properly for all tasks.
-
Morris Jette authored
No change in logic
-
Morris Jette authored
The debugger symbol in srun is not being properly handled today. This change does the malloc once, even for a pack-job, makes the array over-sized, and range checks before writes. Suitable for making srun progress without memory errors (writing off end of allocated memory in an array).
-
Morris Jette authored
-
- 15 Jul, 2017 1 commit
-
-
Morris Jette authored
-
- 14 Jul, 2017 4 commits
-
-
Tim Shaw authored
-
Morris Jette authored
Major re-write of task state container logic to support for list of containers rather than one container per srun command.
-
Isaac Hartung authored
Modify all daemons to re-open log files on receipt of SIGUSR2 signal. This is much than using SIGHUP to re-read the configuration file and rebuild various tables. bug 3070
-
Danny Auble authored
debug.
-
- 13 Jul, 2017 12 commits
-
-
Morris Jette authored
-
Morris Jette authored
No changes to logic
-
Morris Jette authored
-
Tim Shaw authored
bug 3979
-
Isaac Hartung authored
-
Tim Wickberg authored
-
Danny Auble authored
Bug 3967
-
Isaac Hartung authored
-
Danny Auble authored
Bug 3979 and 3989
-
Danny Auble authored
This reverts commit d49081df.
-
Danny Auble authored
Bug 3979 and 3989
-
Dominik Bartkiewicz authored
-
- 11 Jul, 2017 1 commit
-
-
Danny Auble authored
This isn't a memory leak, but does show memory not freed.
-
- 10 Jul, 2017 1 commit
-
-
Ole H Nielsen authored
-
- 08 Jul, 2017 2 commits
-
-
Morris Jette authored
No changes in logic
-
Morris Jette authored
Test was failing sometimes due to varying Expect buffering
-
- 07 Jul, 2017 8 commits
-
-
Danny Auble authored
will have a time displayed when truncating time. Bug 3940.
-
Alejandro Sanchez authored
Otherwise we can end up printing Start times greater than End times, leading to confusion when reading sacct output. 0 is displayed as Unknown. Cosmetic change. Bug 3940.
-
Morris Jette authored
Now have one launch step per pack job component, so no duplicate launch errors
-
Morris Jette authored
-
Alejandro Sanchez authored
This behavior was introduced in bug 2504, commit 7fb0c981 and bug 2643 commit 988edf12 respectively. The reasoning is that sysadmins who see nodes with Reason "Not Responding" but they can manually ping/access the node end up confused. That reason should only be set if the node is trully not responding, but not if the HealthCheckProgram execution failed or returned non-zero exit code. For that case, the program itself would take the appropiate actions, such as draining the node and setting an appropiate Reason. Bug 3931
-
Dominik Bartkiewicz authored
-
Dominik Bartkiewicz authored
-
Morris Jette authored
Use it for setting output label when the output/error file name includes the "%N" format option (node name, e.g. "--output=out.%N").
-