mirror of
https://github.com/mongodb/mongo.git
synced 2024-11-25 09:19:32 +01:00
30 lines
1.4 KiB
Plaintext
30 lines
1.4 KiB
Plaintext
# Death test signal reports cause test failures because the report can't be
|
|
# parsed as JSON. Suppress those messages specifically.
|
|
signal:src/mongo/unittest/death_test.cpp
|
|
|
|
# For some reason there is a race condition in mktime and we need to not alert for that
|
|
race:tzset_internal
|
|
|
|
# WiredTiger is known to cause false positives for data races because it uses a
|
|
# nonstandard thread model that TSAN doesn't know how to deal with. We have
|
|
# already denylisted WiredTiger in TSAN, but that only affects threads created
|
|
# within the WiredTiger source. For threads that call *into* WiredTiger, we
|
|
# need to add suppressions so we still get any potential failures from
|
|
# elsewhere.
|
|
#
|
|
# This is a temporary addition for now because it's possible that these are
|
|
# real positives that we need to do something with. However, because we know
|
|
# that false positives are more likely, we're deferring them until we have
|
|
# fixed the ones we know are real.
|
|
# TODO: https://jira.mongodb.org/browse/SERVER-48599
|
|
race:src/third_party/wiredtiger/*
|
|
|
|
# These functions call malloc() down the line while inside a signal handler.
|
|
# Since we've never had problems with any of the allocators we use, and since
|
|
# the process is going to exit in actual practice (unlike in some of our tests),
|
|
# we are taking the calculated risk to allow AS-unsafe calls in our signal
|
|
# handlers.
|
|
signal:abruptQuitAction
|
|
signal:abruptQuitWithAddrSignal
|
|
signal:StackTraceSigAltStackTest::tryHandler
|