1. 03 Nov, 2020 1 commit
  2. 09 Oct, 2020 2 commits
  3. 08 Oct, 2020 3 commits
  4. 06 Oct, 2020 1 commit
  5. 30 Sep, 2020 3 commits
  6. 29 Sep, 2020 3 commits
  7. 02 Sep, 2020 2 commits
  8. 07 Apr, 2020 2 commits
  9. 09 Jan, 2020 2 commits
  10. 08 Jan, 2020 1 commit
  11. 07 Jan, 2020 4 commits
  12. 10 Dec, 2019 3 commits
  13. 05 Dec, 2019 5 commits
  14. 04 Dec, 2019 3 commits
  15. 11 Oct, 2019 3 commits
    • Lubomir Bulej's avatar
      Try bumping the test time limit to 45 seconds · c34d7ce8
      Lubomir Bulej authored
      Again, this is to accomodate the "dispatchmp" test on slower
      machines (it takes 14-15 seconds on a modern machine).
      c34d7ce8
    • Lubomir Bulej's avatar
      Increase test time limit to 20 seconds · 93054bab
      Lubomir Bulej authored
      This may be necessary for the "dispatchmp" test to finish
      on slower machines.
      93054bab
    • Lubomir Bulej's avatar
      Fix race in "dispatchmp" test and repeatedly force GC · 54396d6c
      Lubomir Bulej authored
      The race was in the code displaying the "So far received..." message.
      After the check if the counter value modulo 1000000 was zero, the
      value actually displayed was queried again, potentially obtaining a
      different value (another thread might have incremented the counter).
      
      To force the client to send notifications about garbage collected
      objects, the client code forces the GC repeatedly and waits a bit
      between the attempts.
      54396d6c
  16. 09 Oct, 2019 2 commits