1. 18 Aug, 2018 2 commits
  2. 17 Aug, 2018 1 commit
    • Morris Jette's avatar
      This patch is for v17.11 and fixes several problems: · 94df0b8c
      Morris Jette authored
      1. The cpu frequency set by the user is not exact with
         current kernels, but close. This changes the logic accordingly.
      2. The original logic would cause the test to hang indefinitely
         if the submitted job never ends. This adds timeout checks
         on the job wait, plus adds a 1 minute time limit on the job.
      3. Improve/simplify the parsing logic.
      
      Bug 5584
      94df0b8c
  3. 16 Aug, 2018 7 commits
  4. 15 Aug, 2018 2 commits
  5. 14 Aug, 2018 4 commits
  6. 13 Aug, 2018 3 commits
  7. 11 Aug, 2018 5 commits
  8. 10 Aug, 2018 2 commits
  9. 09 Aug, 2018 3 commits
  10. 08 Aug, 2018 7 commits
  11. 07 Aug, 2018 3 commits
  12. 06 Aug, 2018 1 commit
    • Tim Wickberg's avatar
      Change debug messages() in _launch_handler(). · c3c78acd
      Tim Wickberg authored
      After changes to slurm_send_only_node_msg(), this message is much
      more likely to appear on systems with overloaded interconnects since
      that connection handling code may end up retransmitting messages
      that were actually received (but that the transmit side could not
      verify were delivered successfully).
      
      As the error() message stated, this isn't actually an error, and
      the code will proceed happily past this point. So drop the debug
      level, and remove the surrealist "this is not an error" part.
      
      Bug 5164.
      c3c78acd