-
Notifications
You must be signed in to change notification settings - Fork 168
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
Comments
Begin Thread_CondvarNotifyAllWakeup
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. |
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). |
This PR #7206 has disabled the builder. |
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 |
thanks @kiburtse |
➤ PM Bot commented: Jira ticket: RCORE-1906 |
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
The text was updated successfully, but these errors were encountered: