-
Notifications
You must be signed in to change notification settings - Fork 361
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
disable tls with Box::leak test on solaris/illumos. #3675
Conversation
Instead of ignoring the test on the target, can you add miri/tests/pass/tree_borrows/tree-borrows.rs Lines 1 to 3 in 60a7200
|
I think you need multiple revisions as in the example. Does the test now fail on Linux if you add a leak to it? |
on these platforms, thread_local is disabled as there is no support for cleanup callback, the test is leaking here.
I don't see why this test should be ignored on Solarish. It shows that we are not properly recognizing main thread TLS variables as being allowed-to-leak -- that should be fixed, not ignored. There is no cleanup callback called here on any platform, since |
Also, other tests like tls_macro_drop and tls_static work fine. "on these platforms, thread_local is disabled" does not seem to be correct. The cleanup callback is called when it is needed. So I don't follow your PR description either. |
@devnexen what are your plans for this PR? Looking at the test, what happens here is that the logic for ignoring memory leaks in the main thread TLS state does not work on Solarish. We already have So to move this forward, please update not only the patch but also the PR description. The explanation for why we want to ignore some targets is: Also, if the goal of the PR is to make more tests pass on Solarish, please adjust |
Thinking about this some more, it's probably best if that test just checks I implemented that in #3822, so that supersedes this PR. Thanks for looking into this! |
Thanks. Sorry I put it aside I no longer access my illumos VM at the moment. |
on these platforms, thread_local is disabled as there is no support for cleanup callback, the test is leaking here.