-
Notifications
You must be signed in to change notification settings - Fork 13.6k
[compiler-rt] ThreadDescriptorSize
is flaky (fails if other tests call InitTlsSize()
first)
#112399
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
Labels
Comments
Oh, that test assumes that |
This assertions was introduced in 999313d, so perhaps that's why it haven't exploded in anyone else's face yet. There are two other tests that indirectly call
And indeed, the first one is being called earlier in the same worker:
|
ThreadDescriptorSize
failing (on some systems) since aa44f59abf399f81585898fb95e66518ef3591afThreadDescriptorSize
is flaky (fails if other tests call InitTlsSize()
first)
vitalybuka
added a commit
that referenced
this issue
Oct 15, 2024
Important part of the test to have correct `ThreadDescriptorSize` after `InitTlsSize()`. It's not a problem if another test called `InitTlsSize()` before. Fixes #112399.
DanielCChen
pushed a commit
to DanielCChen/llvm-project
that referenced
this issue
Oct 16, 2024
Important part of the test to have correct `ThreadDescriptorSize` after `InitTlsSize()`. It's not a problem if another test called `InitTlsSize()` before. Fixes llvm#112399.
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Today, two tests started failing for me on main:
A bisect points out that the failure started happening with aa44f59. Curious facts:
-j12
, the good one is-j32
; I'm going to test later if switching the other to-j12
triggers the issue.TEST(SanitizerCommon, PrintThreadHistory)
), they start passing again.All this considered, my educated guess is that something is leaking from some other test, and the addition of this one caused other tests to be reorganized into shards that trigger this failure.
The text was updated successfully, but these errors were encountered: