- 17 Aug, 2018 8 commits
-
-
Tim Wickberg authored
Use the already-established slurmctld_primary bool instead.
-
Tim Wickberg authored
The second NULL check is a duplicate of the first. The first check is also unnecessary - this field existing is managed by the control_cnt variable. (At one point in development control_cnt did not exist, and control_machine was a 0-terminated array instead.)
-
Tim Wickberg authored
Otherwise cross-architecture failover will break in confusing ways.
-
Tim Wickberg authored
Bug 5256.
-
Danny Auble authored
plugin. Bug 5583
-
Brian Christiansen authored
Caught by verify_lock() annotation in job_submit_plugin_modify(). Bug 5578.
-
Brian Christiansen authored
Caught by verify_lock() annotations in validate_job_create_req() and job_allocate() respectively. Bug 5578.
-
Danny Auble authored
Brian approved
-
- 16 Aug, 2018 29 commits
-
-
Danny Auble authored
Brian approved
-
Danny Auble authored
Brian approved
-
Danny Auble authored
This is only to quite coverity. I don't think this is a real problem. Brian approved.
-
Danny Auble authored
Fix coverity 187747
-
Danny Auble authored
-
Tim Wickberg authored
-
Danny Auble authored
-
Danny Auble authored
(i.e. gres=gpu/tesla) it would get a count of 0.
-
Brian Christiansen authored
Bug 5570
-
Tim Wickberg authored
-
Tim Wickberg authored
-
Dominik Bartkiewicz authored
Note that pipe2() is Linux-specific, but this whole cgroup plugin is already Linux-specific in design, and the eventfd() call itself is Linux-specific as well. Bug 5570.
-
Danny Auble authored
-
Danny Auble authored
Didn't realize centos 6 was so far behind.
-
Felip Moll authored
Bug5503
-
Brian Christiansen authored
-
Danny Auble authored
-
Danny Auble authored
-
Brian Christiansen authored
"IN" tres_usage is reads "OUT" tres_usage is writes page faults are only "ins"
-
Brian Christiansen authored
In 18.08 the jobacct_info stats were changed to tres_usage arrays which are init'ed to INFINITE64 but < 18.08 it was init'ed to 0's. Bug 5554
-
Brian Christiansen authored
-
Brian Christiansen authored
In 18.08, usage values are stored as bytes but in <18.08 values were stored in KB, MB, etc. Also handle cputime adjustments. Related commit: efc161ef.
-
Brian Christiansen authored
In 18.08, VMSIZE is stored as bytes and not kilos anymore. Related commit: c9448c80
-
Brian Christiansen authored
Since cputime isn't stored a double anymore, but as a uin64_t, the cputime is adjusted so that precision isn't lost. Related commit: efc161ef
-
Brian Christiansen authored
In 18.08, the stats are stored in TRES arrays and uses the slurmdb_find_tres_count_in_string() function to return the TRES value. If a value doesn't exist, the function returns INFINITE64. But < 18.08 is expecting NO_VAL values. e.g. A TRES position of INFINTE caused a lappy0 node to be shown -- I don't have a lappy0. brian@lappy:~/slurm/master/lappy$ sacct -j 232809 -o MaxVMSizeNode MaxVMSizeNode -------------- lappy0
-
Brian Christiansen authored
In 18.08, the usage is stored in a TRES arrays and uses the slurmdb_find_tres_count_in_string() function to return the TRES value. If a value doesn't exist, the function returns INFINITE64. But < 18.08 is expecting NO_VAL values.
-
Danny Auble authored
-
Danny Auble authored
Turns out if you don't close up everything you open the hdf5 lib doesn't like that.
-
Danny Auble authored
Fixs regression in 011b2f23.
-
- 15 Aug, 2018 3 commits
-
-
Tim Wickberg authored
Alphabetize target list while here.
-
Danny Auble authored
Bug 4918
-
Danny Auble authored
-