1. 14 Aug, 2017 1 commit
  2. 11 Aug, 2017 7 commits
  3. 10 Aug, 2017 1 commit
  4. 08 Aug, 2017 1 commit
  5. 07 Aug, 2017 4 commits
  6. 04 Aug, 2017 6 commits
  7. 02 Aug, 2017 4 commits
  8. 01 Aug, 2017 4 commits
  9. 31 Jul, 2017 1 commit
  10. 28 Jul, 2017 5 commits
  11. 27 Jul, 2017 2 commits
    • Alejandro Sanchez's avatar
      Fix bug when tracking multiple simultaneous spawned ping cycles · f7463ef5
      Alejandro Sanchez authored
      When more than 1 ping cycle is spawned simultaneously (for instance
      REQUEST_PING + REQUEST_NODE_REGISTRATION_STATUS for the selected nodes),
      we do not track a separate ping_start time for each cycle. When ping_begin()
      is called, the information about the previous ping cycle is lost. Then when
      ping_end() is called for the first of the two cycles, we set ping_start=0,
      which is incorrectly used to see if the last cycle ran for more than
      PING_TIMEOUT seconds (100s), thus incorrectly triggering the:
      
       error("Node ping apparently hung, many nodes may be DOWN or configured "
             "SlurmdTimeout should be increased");
      
      Bug 3914
      f7463ef5
    • Tim Shaw's avatar
      04b431b4
  12. 26 Jul, 2017 4 commits