- 27 Aug, 2015 12 commits
-
-
Danny Auble authored
to free it otherwise.
-
Danny Auble authored
198aa220
-
Morris Jette authored
-
Morris Jette authored
Save state, even when no buffers are allocated. Set "last_update_time" on the buffer in some places where it was missing. Make sure we save state at shutdown.
-
Thomas Cadeau authored
-
Brian Christiansen authored
Bug 1826
-
Danny Auble authored
-
Danny Auble authored
since this should never happen unless we don't have state files.
-
Danny Auble authored
-
Danny Auble authored
association manager.
-
Pythagoras Watson authored
In pam_setup, correct comments for typos and to match the code. On failure, properly deallocate the PAM resources and ensure the PAM handle is null so as to make calling pam_finish always safe. In pam_finish, always try to deallocate all the PAM resources. Also, ensure the PAM handle is null so as to make calling pam_finish always safe. This allows for calling pam_finish multiple times without error.
-
Morris Jette authored
This adds a simple test for persistent burst buffer creation and deletion for the burst_buffer/cray plugin.
-
- 26 Aug, 2015 15 commits
-
-
Morris Jette authored
Remove "is_job_array" argument to bb_g_job_validate2() function. Defer starting job that needs persistent burst buffer until it has been created. Avoid trying to create persistent burst buffer with duplicate name
-
Danny Auble authored
-
Morris Jette authored
This will be needed for TRES limit enforcement
-
Morris Jette authored
This is a more thorough treatment of bug 1790 and commit d2545ca746ea0a2f9653664a601052cfd5eb8ad It clears the task_id_bitmap once the last task is scheduled and task_cnt becomes zero
-
Morris Jette authored
-
Morris Jette authored
Prevent job array task ID from being reported as NO_VAL if last task in the array gets requeued. The problem is that when that task starts, the task bitmap entry for it stays set, but the task counter gets decremented. If that job then gets requeued, under some conditions a failure to schedule it results in the array_task_id in the job record getting set to NO_VAL. Then when building the job info to report for squeue/scontrol, the string showing the pending task ID's is not rebuilt due to that counter being zero. All indications are that the job runs fine, only the information reported to squeue/scontrol is wrong. bug 1790
-
Thomas Cadeau authored
-
David Bigagli authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
accounting correctly to avoid meaningless errors about overflow.
-
Morris Jette authored
-
- 25 Aug, 2015 13 commits
-
-
Brian Christiansen authored
-
Brian Christiansen authored
Conflicts: config.h.in src/sreport/job_reports.c
-
Nathan Yee authored
-
Brian Christiansen authored
Bug 1873
-
Morris Jette authored
-
Morris Jette authored
Fix shutdown race condition that could cause the plugin to deadlock. Improve validation of burst buffer options. Hold job with an burst_buffer specification later discovered to be bad.
-
Morris Jette authored
-
Danny Auble authored
intended for the head of the tree.
-
Morris Jette authored
Handle out-of-band (i.e. outside of Slurm) persistent burst buffer creation/deletion with respect to their reservations, as used for limit enforcement.
-
Douglas Jacobsen authored
-
Nathan Yee authored
-
David Bigagli authored
-
Morris Jette authored
Avoid creating a duplicate burst buffer record due to a race condition between the "create_persistent" thread and the "load_state" thread.
-