Skip to content
GitLab
  1. 26 May, 2015 2 commits
  3. 23 May, 2015 2 commits
  5. 22 May, 2015 2 commits
  7. 21 May, 2015 2 commits
  9. 20 May, 2015 3 commits
  11. 19 May, 2015 1 commit
  13. 18 May, 2015 2 commits
  15. 16 May, 2015 1 commit
  17. 15 May, 2015 3 commits
  19. 14 May, 2015 7 commits
  21. 13 May, 2015 6 commits
  23. 12 May, 2015 3 commits
  25. 11 May, 2015 2 commits
    • Morris Jette's avatar
      Explain job option of --mem=0 means all memory · c0d6edc9
      Morris Jette authored 
      This is a special case. This change documents the way Slurm has
always worked.
      c0d6edc9
    • Morris Jette's avatar
      Purge old step data on job requeue · beecc7b0
      Morris Jette authored 
      Make sure that old step data is purged when a job is requeued.
Without this logic, if a job terminates abnormally then old step
data may be left in slurmctld. If the job is then requeued and
started on a different node, referencing that old job step data
can result in abnormal events. One specific failure mode is if
the job is requeued on a node with a different number of cores,
and the step terminated RPC arrives later, the job and step
bitmaps of allocated cores can differ in size generating an
abort.
bug 1660
      beecc7b0
  27. 08 May, 2015 4 commits