-
Notifications
You must be signed in to change notification settings - Fork 13
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
Archer does not correctly call RunningOnValgrind on OSX #76
Comments
I cannot really test this, but I think it should be I still don't understand what is going on with the tests. Are we sure, that the code is executed concurrently and not sequentially under OSX? I changed the tests to not use sleep, but signaling in: https://reviews.llvm.org/D45890 |
I think, I found another issue with the current implementation: Initialization of the static variable runOnTsan might be a problem. I pushed fixes for the two issues to fix-runOnTsan. Please test whether this fixes your issues. |
I tried it, it seems better but it can't identify all the races in the task tests, and still a lot of false positives. Failing Tests (19): |
On Mac OSX "runOnTsan" is always initialized to 0 which consequently does not initialize the OMPT runtime. The races in the test suite are correctly reported but it reports false positives in the test with no races. On the other end if we force
runOnTsan=1
no false positive is reported but Archer does not detect any race in the racy tests.The text was updated successfully, but these errors were encountered: