-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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 readytorun/GenericCycleDetection/Depth3Test/Depth3Test.sh #88586
Comments
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsFailed in: runtime-coreclr gcstress-extra 20230709.1 Failed tests:
Error message:
Stack trace:
More failures
|
This does not look like a JIT issue, but rather a timeout under gcstress for the test added by @trylek in #71426 (note that it seems we run crossgen2 itself under gcstress). @trylek can you please consider if we should just disable the test under GC stress, and whether it is expected to take a long time under gc stress? |
Failed in: runtime-coreclr outerloop 20230722.4 Failed tests:
Error message:
Stack trace:
More failures
|
Failed in: runtime-coreclr jitstress2-jitstressregs 20230730.1 Failed tests:
Error message:
Stack trace:
More failures
|
@kunalspathak When marking an issue with Known Build Error you also have to fill in the "known error" JSON, otherwise the bot won't pick up the error. (edit: I've added a known error message now) |
Failed again in: runtime-coreclr jitstress-isas-x86 20230805.1 Failed tests:
Error message:
Stack trace:
More failures
|
Failed again in: runtime-coreclr gcstress0x3-gcstress0xc 20230812.1 Failed tests:
Error message:
Stack trace:
More failures
|
Fixed with #90777, closing. |
Failed in: runtime-coreclr gcstress-extra 20230709.1
Failed tests:
Error message:
Stack trace:
More failures
Known Issue Error Message
Fill the error message using step by step known issues guidance.
Report
Summary
The text was updated successfully, but these errors were encountered: