mirror of https://mirror.osredm.com/root/redis.git
b7c6755b1b
Add thread sanitizer run to daily CI. Few tests are skipped in tsan runs for two reasons: * Stack trace producing tests (oom, `unit/moduleapi/crash`, etc) are tagged `tsan:skip` because redis calls `backtrace()` in signal handler which turns out to be signal-unsafe since it might allocate memory (e.g. glibc 2.39 does it through a call to `_dl_map_object_deps()`). * Few tests become flaky with thread sanitizer builds and don't finish in expected deadlines because of the additional tsan overhead. Instead of skipping those tests, this can improved in the future by allowing more iterations when waiting for tsan builds. Deadlock detection is disabled for now because of tsan limitation where max 64 locks can be taken at once. There is one outstanding (false-positive?) race in jemalloc which is suppressed in `tsan.sup`. Fix few races thread sanitizer reported having to do with writes from signal handlers. Since in multi-threaded setting signal handlers might be called on any thread (modulo pthread_sigmask) while the main thread is running, `volatile sig_atomic_t` type is not sufficient and atomics are used instead. |
||
|---|---|---|
| .. | ||
| aofmanifest.tcl | ||
| benchmark.tcl | ||
| cli.tcl | ||
| cluster.tcl | ||
| cluster_util.tcl | ||
| redis.tcl | ||
| response_transformers.tcl | ||
| server.tcl | ||
| test.tcl | ||
| tmpfile.tcl | ||
| util.tcl | ||