Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TSAN issue: ThreadSanitizer:DEADLYSIGNAL #7185

Open
nicola-cab opened this issue Dec 6, 2023 · 6 comments
Open

TSAN issue: ThreadSanitizer:DEADLYSIGNAL #7185

nicola-cab opened this issue Dec 6, 2023 · 6 comments

Comments

@nicola-cab
Copy link
Member

[2023/12/06 11:01:12.367] 1: ThreadSanitizer:DEADLYSIGNAL
[2023/12/06 11:01:12.367] 1: ThreadSanitizer:DEADLYSIGNAL
[2023/12/06 11:01:12.367] 1: ThreadSanitizer: nested bug in the same thread, aborting.
[2023/12/06 11:01:12.482] 1/1 Test #1: CoreTests ........................***Failed   96.64 sec
[2023/12/06 11:01:12.482] 0% tests passed, 1 tests failed out of 1

https://spruce.mongodb.com/task/realm_core_stable_macos_1100_arm64_tsan_core_tests_pat[…]6570528261837d6f32012af9_23_12_06_10_52_51/logs?execution=0

Core version

Core version: 13.24.0

@kiburtse kiburtse changed the title TSAN issue reported in Begin Thread_CondvarNotifyAllWakeup TSAN issue: ThreadSanitizer:DEADLYSIGNAL Dec 7, 2023
@kiburtse
Copy link
Contributor

kiburtse commented Dec 7, 2023

It is not specific to any test. It started to happen right after #6911. We essentially started to run with sanitizers on production like fully optimized builds, and this builder macos_1100_arm64 is what was added. It wasn't tested before with sanitizers at all. This error happens on many tests in pure core and sync test suites only. After searching a bit on this problem, it looks to as compiler and sanitizers implementation issue. I don't think that we can do anything for this other than update the testing platform and the compiler.

@nicola-cab
Copy link
Member Author

nicola-cab commented Dec 8, 2023

OK, the only problem I have is that these checks (that are needed) if they can fail spuriously, will make releases unpredictable sometimes, or in general trigger false positives. Ideally, we want to avoid re-running things for false positives (does the same apply to evergreen and Jenkins).
However, if you think there is no solution. Probably I can close this.

@nicola-cab
Copy link
Member Author

This PR #7206 has disabled the builder.

@kiburtse kiburtse reopened this Mar 20, 2024
@kiburtse
Copy link
Contributor

kiburtse commented Mar 20, 2024

since #7383 reenabled these tests, it's the problem once again

I've put the fix to run this builder on newer macos13 here #7472 as a possible solution

@nicola-cab
Copy link
Member Author

thanks @kiburtse

Copy link

sync-by-unito bot commented Mar 20, 2024

➤ PM Bot commented:

Jira ticket: RCORE-1906

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants