- 03 Jul, 2018 5 commits
-
-
Morris Jette authored
Add 64-bit sched_weight (scheduling weight) to node_set struct Populate it with the node's weight (possibly reboot weight) plus high-order bits for FLEX-reservation and rebooting. No longer are node weights of INFINITE or (INFINITE-1) used to flag FLEX or reboot requirements so we don't need to worry about overlapping node weight values. It also will cleanly allow the cons_tres plugin to be passed ALL usable nodes at one time to accumulate resources from the lowest weight first and only use individual higher weight nodes as needed (rather than possibly using mostly higher weight nodes). bug 4821
-
Felip Moll authored
breaks out node sets by in/out flex reservation and need to reboot bug 4821
-
Morris Jette authored
The node weight of a node requiring reboot is not a fixed value in v18.08, but configurable bug 4821
-
Morris Jette authored
bug 5337
-
Broderick Gardner authored
bug 5337
-
- 02 Jul, 2018 9 commits
-
-
Broderick Gardner authored
bug 5337
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
This test change addresses gres api changes introduced in commit 6e0469b5
-
Morris Jette authored
-
Morris Jette authored
Implicitly set node count, task count, ntasks_per_* as appropriate
-
Morris Jette authored
Prior logic lacked a line-feed and ran lines together
-
- 29 Jun, 2018 5 commits
-
-
Morris Jette authored
-
Morris Jette authored
Previous logic was implicitly starting 2 tasks due to the combination of --gpus and --gpus-per-node
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
- 27 Jun, 2018 1 commit
-
-
Morris Jette authored
Original logic was testing against number of available CPUs on a node, not the number actually being allocated. This can easily result in a valid job not being possible to run. Note that setting the max_cpus parameter requires the "scontrol update jobid=# numcpus=#-#" command be explicitly executed as the option is not available at job submit time, so it isn't something likely to happen on a production system. Also note this bug exists in the cons_res plugin and was just copied to cons_tres.
-
- 26 Jun, 2018 6 commits
-
-
Morris Jette authored
-
Morris Jette authored
-
Felip Moll authored
-
Felip Moll authored
When one asks for an inactive feature and also specifies the node with -w flag, the node will be rebooted despite it may contain running jobs. bug4821
-
Morris Jette authored
Return resource array structure rather than just CPU count
-
Tim Wickberg authored
and avoid race condition calling task before proctrack can introduce. Bug 5319
-
- 25 Jun, 2018 3 commits
-
-
Morris Jette authored
to work correctly. Bug 5155 Bug 4516
-
Morris Jette authored
delayed until the first job completes execution and it's burst buffer stage-out is completed. Bug 4675
-
Morris Jette authored
-
- 22 Jun, 2018 7 commits
-
-
Morris Jette authored
If MailProg is not configured and "/bin/mail" (the default) does not exist, but "/usr/bin/mail" does exist then use "/usr/bin/mail" as a default value.
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
Rather than eliminating cores in order across sockets, try to remove cores evenly across the sockets in order to preserve access to sockets which might have GPUs we want to use.
-
Dominik Bartkiewicz authored
Bug 5191
-
Dominik Bartkiewicz authored
Bug 5159.
-
- 21 Jun, 2018 3 commits
-
-
Morris Jette authored
This will clear unusable cores from the bitmap as needed.
-
Morris Jette authored
-
Morris Jette authored
-
- 20 Jun, 2018 1 commit
-
-
Morris Jette authored
Coverity CID 186635 and 186636 (same leak, two paths to the same place)
-