1. 27 Oct, 2020 3 commits
  2. 10 Sep, 2020 1 commit
  3. 01 Sep, 2020 6 commits
  4. 20 Jul, 2020 3 commits
  5. 28 May, 2020 2 commits
  6. 25 May, 2020 1 commit
  7. 08 May, 2020 1 commit
    • Oran Agra's avatar
      add daily github actions with libc malloc and valgrind · 3d3861dd
      Oran Agra authored
      * fix memlry leaks with diskless replica short read.
      * fix a few timing issues with valgrind runs
      * fix issue with valgrind and watchdog schedule signal
      
      about the valgrind WD issue:
      the stack trace test in logging.tcl, has issues with valgrind:
      ==28808== Can't extend stack to 0x1ffeffdb38 during signal delivery for thread 1:
      ==28808==   too small or bad protection modes
      
      it seems to be some valgrind bug with SA_ONSTACK.
      SA_ONSTACK seems unneeded since WD is not recursive (SA_NODEFER was removed),
      also, not sure if it's even valid without a call to sigaltstack()
      3d3861dd
  8. 17 Apr, 2020 1 commit
    • Oran Agra's avatar
      testsuite run the defrag latency test solo · 6148f949
      Oran Agra authored
      this test is time sensitive and it sometimes fail to pass below the
      latency threshold, even on strong machines.
      
      this test was the reson we're running just 2 parallel tests in the
      github actions CI, revering this.
      6148f949
  9. 07 Apr, 2020 1 commit
  10. 27 Feb, 2020 2 commits
    • Oran Agra's avatar
      fix github actions failing latency test for active defrag - part 2 · 635321d4
      Oran Agra authored
      it seems that running two clients at a time is ok too, resuces action
      time from 20 minutes to 10. we'll use this for now, and if one day it
      won't be enough we'll have to run just the sensitive tests one by one
      separately from the others.
      
      this commit also fixes an issue with the defrag test that appears to be
      very rare.
      635321d4
    • Oran Agra's avatar
      fix github actions failing latency test for active defrag · 0b988fa9
      Oran Agra authored
      seems that github actions are slow, using just one client to reduce
      false positives.
      
      also adding verbose, testing only on latest ubuntu, and building on
      older one.
      
      when doing that, i can reduce the test threshold back to something saner
      0b988fa9
  11. 20 Oct, 2019 1 commit