-
Notifications
You must be signed in to change notification settings - Fork 10.6k
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
No pie #5809
No pie #5809
Conversation
Was this also a workaround for some previous problem? On Thu, Mar 17, 2016, 5:28 PM Craig Tiller notifications@github.com wrote:
|
It was. An older TSAN needed it IIRC. This seems to fix the TSAN issues... On Thu, Mar 17, 2016, 5:31 PM Vijay Pai notifications@github.com wrote:
|
Very interesting. Yes, I can take a look at the real tsan issue today. It all seems to be from Initializer, which is always interesting. Correction: 8 caused by initializing, 1 from connectivity-state. |
The remaining tsan failure after #5843 is something that I started to fix previously in #5489 but closed because we hadn't really seen it in the wild and it might be a false positive - but I think that I need to put it back in, cleanly if possible. Specifically, commit 9d92cc6 is potentially useful (or something like it), but the other commit in that PR needs a solution that will properly handle #5656 . |
No description provided.