mirror of
https://codeberg.org/redict/redict.git
synced 2025-01-23 00:28:26 -05:00
665e428435
I recently started seeing a lot of empty valgrind reports in the daily CI. i.e. prints showing valgrind header but no leak report, which causes the tests to fail https://github.com/redis/redis/runs/3991335416?check_suite_focus=true This commit change 2 things: * first, considering valgrind is just slow, we used to give processes 60 seconds timeout on shutdown instead of 10 seconds we give normally. this commit changes that to 120. * secondly, when we reach the timeout, we first try to use SIGSEGV so that maybe we'll get a stack trace indicating where redis is hang, and we only resort to SIGKILL if double that time passed. note that if there are indeed hang processes, we will normally not see that in the non-valgrind runs, since the tests didn't use to detect any failure in that case, and now they will since `crashlog_from_file` is run after `kill_server`. |
||
---|---|---|
.. | ||
benchmark.tcl | ||
cli.tcl | ||
cluster.tcl | ||
redis.tcl | ||
server.tcl | ||
test.tcl | ||
tmpfile.tcl | ||
util.tcl |