1. 28 Jan, 2015 1 commit
  2. 27 Jan, 2015 1 commit
  3. 26 Jan, 2015 1 commit
  4. 23 Jan, 2015 2 commits
  5. 22 Jan, 2015 2 commits
  6. 21 Jan, 2015 4 commits
    • Morris Jette's avatar
      fix job array scheduling anomaly · 3787c01f
      Morris Jette authored
      If some tasks of a job array are runnable and the meta-job array
      record is not runable (e.g. held), the old logic could start a
      runable task then try to start the non-runable meta-job, discover
      it can not run, and set its reason to "BadConstraints".
      
      Test case:
      Make it so no jobs can start (partition stopped, slurmd down, etc.)
      submit a job array
      hold the job array
      release the first two tasks of the job array
      Make it so jobs can start
      3787c01f
    • Morris Jette's avatar
      fix squeue merging of job arrays · 261580be
      Morris Jette authored
      Squeue modified to not merge tasks of a job array if their wait reasons
      differ.
      bug 1388
      261580be
    • Morris Jette's avatar
      Added power management plugin infrastructure · 34986d29
      Morris Jette authored
      No functions currently exist, only the plugin wrapper and stubbed functions.
      34986d29
    • Morris Jette's avatar
      Note new config parameters · 290106cd
      Morris Jette authored
      290106cd
  7. 20 Jan, 2015 3 commits
  8. 19 Jan, 2015 1 commit
  9. 17 Jan, 2015 1 commit
  10. 15 Jan, 2015 3 commits
    • Danny Auble's avatar
      Make CR_ONE_TASK_PER_CORE work correctly with task/affinity. · db926ab7
      Danny Auble authored
      What this does is use the core level binding after each task is laid out
      to skip all the extra threads in the core so it doesn't give them to
      another task.
      
      It probably isn't perfect, but does solve all the scenarios I found.
      db926ab7
    • Morris Jette's avatar
      GRES scheduling fix · 72cefd54
      Morris Jette authored
      Fix for GRES scheduling in which there is CPU topology defined or
      GRES types defined and there is more than 1 GPU per topology record
      in slurmctld. Without this fix, only one GRES could be allocated
      from each defined topology.
      bug 1369
      72cefd54
    • Morris Jette's avatar
      Fix for slurmctld abort on gres error · ce1d99f5
      Morris Jette authored
      The slurmctld could abort with a gres configuration having
      Type= configured, but no CPU binding configured.
      ce1d99f5
  11. 14 Jan, 2015 3 commits
  12. 13 Jan, 2015 3 commits
  13. 12 Jan, 2015 2 commits
  14. 09 Jan, 2015 2 commits
  15. 08 Jan, 2015 1 commit
  16. 07 Jan, 2015 5 commits
  17. 06 Jan, 2015 5 commits