-
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
Test failure JIT/Regression/JitBlue/Runtime_40444/Runtime_40444/Runtime_40444.sh #50761
Comments
@VincentBu can we get the failure history of this test from Kusto query? |
@JulieLeeMSFT , Hi, I can't get the failure history of this test from Kusto query. |
@VincentBu - I am curious how do you spot failures and decide for which ones to open an issue? The query only returns the test failures for scheduled runs and not for manually triggered or the ones that got triggered from PR. The runtime-coreclr gcstress-extra Checked-gcstress0xc_jitstress2 failed from manual trigger . Since it was failing on main, we might see that the query would return result for this test failures in next week or so. @BruceForstall - FYI. |
Failed again in runtime-coreclr gcstress-extra 20210717.1 Failed test:
One of error messages:
|
probably fixed by #56059, it looks like it was failing in 50% runs so I triggered 4 to confirm. https://dev.azure.com/dnceng/public/_build?definitionId=662&_a=summary |
I saw this test failing again couple days ago - console.log - #20210822.1:
@sandreenko Should we re-open the issue? |
Failed again in: runtime-coreclr gcstress-extra 20220109.1 Failed test:
Error message:
|
Failed again in: runtime-coreclr outerloop 20220315.2 Failed test:
Error message:
|
This new failure has a different failure mode, so I opened #66690 to track it. |
I don't see this failure in gcstress-extra. |
Failed again in runtime-coreclr gcstress-extra 20210404.2
Failed test:
Error message:
The text was updated successfully, but these errors were encountered: