- 27 Oct, 2020 3 commits
-
-
Yossi Gottlieb authored
Useful for running tests on systems which may be way slower than usual. (cherry picked from commit 843a13e8)
-
- 10 Sep, 2020 1 commit
-
- 01 Sep, 2020 6 commits
-
-
Yossi Gottlieb authored
Avoid re-configuring (and validating) SSL/TLS configuration on `CONFIG SET` when TLS is not actively enabled for incoming connections, cluster bus or replication. This fixes failures when tests run without `--tls` on binaries that were built with TLS support. An additional benefit is that it's now possible to perform a multi-step configuration process while TLS is disabled. The new configuration will be verified and applied only when TLS is effectively enabled. (cherry picked from commit fb2a94af)
-
Yossi Gottlieb authored
(cherry picked from commit 944cca98)
-
Yossi Gottlieb authored
(cherry picked from commit f2da3efc)
-
Yossi Gottlieb authored
(cherry picked from commit 4ac1f9ac)
-
Scott Brenner authored
(cherry picked from commit 2f4e9c3f)
-
- 20 Jul, 2020 3 commits
-
-
Oran Agra authored
-
Abhishek Soni authored
(cherry picked from commit d5648d61)
-
- 28 May, 2020 2 commits
- 25 May, 2020 1 commit
-
-
Oran Agra authored
-
- 08 May, 2020 1 commit
-
-
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()
-
- 17 Apr, 2020 1 commit
-
-
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.
-
- 07 Apr, 2020 1 commit
-
-
Oran Agra authored
-
- 27 Feb, 2020 2 commits
-
-
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.
-
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
-
- 20 Oct, 2019 1 commit
-
-
Guy Korland authored
-