-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Test failure Loader/binding/tracing/BinderTracingTest.ResolutionFlow/BinderTracingTest.ResolutionFlow.cmd #94390
Comments
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsFailed in: runtime-coreclr pgostress 20231103.1 Failed tests:
Error message:
Stack trace:
More failures
|
@davmason, this test is failing again. Please take a look. |
Neue Möglichkeiten |
One failure in the last month on the runtime-coreclr pgostress build definition in the last month, removing "blocking-clean-ci" tag:
|
Failed again in: runtime-coreclr jitstress 20231126.1 Failed tests:
Error message:
Stack trace:
More failures
|
Failed again in: runtime-coreclr gcstress-extra 20231203.1 Failed tests:
Error message:
Stack trace:
More failures
|
Failed again in: runtime-coreclr jitstress-isas-x86 20231212.1 Failed tests:
Error message:
Stack trace:
More failures
|
When I look at the most recent failure in runtime-coreclr jitstress-isas-x86 20231212.1 I can only see a crash dump for the host process, not the subprocess that the test actually runs in. @JulieLeeMSFT should there be a dump for the subprocess too? |
Failed again in: runtime-coreclr gcstress0x3-gcstress0xc 20240113.1 Failed tests:
Error message:
Stack trace:
More failures
|
Failed again in: runtime-coreclr gcstress0x3-gcstress0xc 20240121.1 Failed tests:
Error message:
Stack trace:
More failures
|
Failed in: runtime-coreclr jitstress2-jitstressregs 20240210.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr gcstress0x3-gcstress0xc 20240225.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr gcstress0x3-gcstress0xc 20240303.1 Failed tests:
Error message:
Stack trace:
|
@davmason, how is the investigation on this test failure going? |
Looking at the recent failures they are all GCStress, and debugging a few of them they all look like they are not hung and just timing out because GCStress is making them take forever to run. I don't think there is currently any issue with EventSource like I was originally tagged in. @JulieLeeMSFT @jakobbotsch @tommcdon do any of you know who owns these tests? Should it be disabled on GCStress? |
@jakobbotsch PTAL.
|
Sounds reasonable to disable it on gcstress to me if it's just a slow test. Going to unassign myself since I don't own these tests and the issue does not seem JIT related. |
It's very possible there's two separate issues. From the gcstress timeouts it definitely does look like the test is just too slow to run under gcstress, so it sounds good to disable it there and then see if we hit the issue in the other configs again. |
Failed in: runtime-coreclr gcstress0x3-gcstress0xc 20240317.1 Failed tests:
Error message:
Stack trace:
More failures
|
Failed in: runtime-coreclr gcstress0x3-gcstress0xc 20240324.1 Failed tests:
Error message:
Stack trace:
More failures
|
Failed in: runtime-coreclr gcstress0x3-gcstress0xc 20240331.1 Failed tests:
Error message:
Stack trace:
More failures
|
@tommcdon do you know who owns this test? I don't believe the current failures are related to EventSource, we should loop in the owner |
Looking at test commit history this seems to be owned by the loader team. Adding @AndyAyersMS @elinor-fung to help find the owner. |
Sorry - meant to add @agocke. @AndyAyersMS please ignore. |
Failed in: runtime-coreclr gcstress0x3-gcstress0xc 20240406.1 Failed tests:
Error message:
Stack trace:
|
@agocke, @elinor-fung, we are looking for the owner of this test. |
Failed at #100787 |
We haven't touched anything here, so I'm not sure why these started to time out. But I agree that nothing appears hung - just too slow to run under some stress configurations. We can disable these on gcstress like what was done for all tracing tests in #85186 |
#100798 disables the tests under gcstress. |
Failed in: runtime-coreclr pgostress 20231103.1
Failed tests:
Error message:
Stack trace:
More failures
The text was updated successfully, but these errors were encountered: