1. 07 Jun, 2016 2 commits
    • Morris Jette's avatar
      Cray NHC underflow on reconfigure · de1400c9
      Morris Jette authored
      Fix for tracking job resource allocation when slurmctld is reconfigured
          while Cray Node Health Check (NHC) is running. Previous logic would fail to
          record the job's allocation then perform release operation upon NHC
          completeion, resulting in underflow error messages.
      bug 2353
      de1400c9
    • Dominik Bartkiewicz's avatar
      Fix hostrange_hn_within to allow for mixed prefix lengths. · 7843e158
      Dominik Bartkiewicz authored
      While here, mark options const, and add leading underscore to denote this
      as a static function (only called within hostlist.c). Also change strcmp
      to xstrcmp.
      
      Commit a6ffef22 changed this function and would alter the input hn,
      which led to subsequent calls to the function having wrong prefix
      lengths for that hostrange precluding it from matching correctly.
      
      Bug 2558.
      7843e158
  2. 06 Jun, 2016 3 commits
  3. 03 Jun, 2016 3 commits
  4. 02 Jun, 2016 7 commits
  5. 01 Jun, 2016 2 commits
  6. 31 May, 2016 6 commits
  7. 27 May, 2016 8 commits
    • Morris Jette's avatar
      Fix for tracking a node's allocated CPUs with gang scheduling. · 372b7e06
      Morris Jette authored
      This bug was introduced by commit 21c52d2f
      which fixed a different problem tracking resources associated with suspended
      jobs. There are subtle differences between jobs that are suspended by a
      user/administrator and jobs suspended by gang scheduling which resulted in
      undercounting allocated CPUs when a job suspended by gang scheduling
      was active at the same time of a slurmctld reconfiguration request.
      See bugs 2353 (original bug related to commit 21c52d2f
      and bug 2765
      372b7e06
    • Danny Auble's avatar
      If no default account is given for a user when creating (only a list of · a621b6d7
      Danny Auble authored
      accounts) no default account is printed, previously NULL was printed.
      
      This is just not printing it, but whole function should probably be
      revisited as the rigmarole can probably be avoided as we always know what
      the default is going to be if none is specified (first off the list).
      
      The problem with that though is if the user has been added to a cluster
      already and they have a default, but then added to a new cluster where
      they don't have a default.  In this case you want to keep the first
      clusters default, but set the default for the second cluster.
      
      Bug 2725
      a621b6d7
    • Danny Auble's avatar
      d1285c9c
    • Tim Wickberg's avatar
      Prevent possible deadlock in acct_gather_filesystem/lustre · 1f4e1430
      Tim Wickberg authored
      Add missing unlock before return. Coverity 44888.
      1f4e1430
    • Morris Jette's avatar
      Revert bad task binding logic · 223da891
      Morris Jette authored
      This reverts commit cc242de3
      That patch fixed bug 2745, but breaks tests 1.89 and 1.91 on
      typical Xeon processors
      223da891
    • Morris Jette's avatar
      Fix for tracking a node's allocated CPUs with gang scheduling. · 4ce62678
      Morris Jette authored
      This bug was introduced by commit 21c52d2f
      which fixed a different problem tracking resources associated with suspended
      jobs. There are subtle differences between jobs that are suspended by a
      user/administrator and jobs suspended by gang scheduling which resulted in
      undercounting allocated CPUs when a job suspended by gang scheduling
      was active at the same time of a slurmctld reconfiguration request.
      See bugs 2353 (original bug related to commit 21c52d2f
      and bug 2765
      4ce62678
    • Danny Auble's avatar
      If no default account is given for a user when creating (only a list of · 9917c49d
      Danny Auble authored
      accounts) no default account is printed, previously NULL was printed.
      
      This is just not printing it, but whole function should probably be
      revisited as the rigmarole can probably be avoided as we always know what
      the default is going to be if none is specified (first off the list).
      
      The problem with that though is if the user has been added to a cluster
      already and they have a default, but then added to a new cluster where
      they don't have a default.  In this case you want to keep the first
      clusters default, but set the default for the second cluster.
      
      Bug 2725
      9917c49d
    • Danny Auble's avatar
      2a817734
  8. 26 May, 2016 1 commit
  9. 25 May, 2016 3 commits
  10. 24 May, 2016 5 commits