diff --git a/.cirrus.yml b/.cirrus.yml index bcc80842bf..78ca2ffe6f 100644 --- a/.cirrus.yml +++ b/.cirrus.yml @@ -390,7 +390,7 @@ ubsan_sanitizer_task: tsan_sanitizer_task: container: # Just uses a recent/common distro to run memory error/leak checks. - dockerfile: ci/ubuntu-20.04/Dockerfile + dockerfile: ci/ubuntu-22.04/Dockerfile << : *SANITIZERS_RESOURCE_TEMPLATE << : *CI_TEMPLATE diff --git a/ci/tsan_suppressions.txt b/ci/tsan_suppressions.txt index f836f44bdf..ded78d13ac 100644 --- a/ci/tsan_suppressions.txt +++ b/ci/tsan_suppressions.txt @@ -17,6 +17,7 @@ race:std::ctype::narrow race:broker::internal::connector::run_impl race:caf::net::multiplexer::set_thread_id race:caf::action::run +mutex:caf::detail::ringbuffer >, 64ul>::push_back # This one causes supervisor.config-bare-mode to fail occasionally but not always signal:caf::actor_control_block::enqueue @@ -32,3 +33,12 @@ race:sqlite3_initialize # This one isn't actually in sqlite code, but some StringVal object gets ref'd by # zeek::id::find_const and throws a data race. race:zeek::logging::writer::detail::SQLite::DoInit + +# These findings were suppressed after the CI build was upgraded to Ubuntu 22.04. +# They weren't reported by prior compiler versions. +race:zeek::threading::MsgThread::RetrieveIn +race:zeek::threading::MsgThread::Run +race:zeek::threading::InputMessage::Object +mutex:zeek::threading::Queue::Put +mutex:zeek::threading::Queue::LocksForAllQueues +deadlock:zeek::threading::Queue::LocksForAllQueues