-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
leakwheel failing in CI #53452
Comments
Tagging subscribers to this area: @BrzVlad Issue Detailshttps://github.com/dotnet/runtime/issues/9615suggests this might be a test bug, probably because it's using
|
Tagging subscribers to this area: @dotnet/gc Issue Detailshttps://github.com/dotnet/runtime/issues/9615suggests this might be a test bug, probably because it's using
|
@BrzVlad @Maoni0 is this a test bug? @aik-jahoda / @akoeplinger can you please help disable this test on android and Linux-x64 for mono. |
@hoyosjs This test is expected to fail on mono, since it seems to rely on finalizers being run in order to determine success of the test. Don't know about the coreclr failures though. |
Test was disabled on Mono. |
For some of the CI failures it seems to have asserted with the following assert, seems like a genuine issue and not a test one. Does this repro on CI runs in main?
|
@hoyosjs is this failing still for coreclr? |
Not that I can see. It's fully disabled on mono, and ARM32 and Win-ARM64 on coreclr. |
Ok, thanks. Closing for now. |
#9615 suggests this might be a test bug, probably because it's using
WaitForPendingFinalizers
.Runfo Tracking Issue: gc/scenarios/leakwheel/leakwheel/leakwheel.sh
Build Result Summary
The text was updated successfully, but these errors were encountered: