-
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 Regressions\\coreclr\\GitHub_45929\\test45929\\test45929.cmd #60152
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Failed again in: runtime-coreclr outerloop 20211015.6 Failed tes:
Error message:
|
Failed again in: runtime-coreclr r2r 20211024.1 Failed test:
Error message:
|
Failed again in: runtime-coreclr outerloop 20211109.3 Failed test:
One of error message:
|
Failed again in: runtime-coreclr jitstress 20220111.1 Failed test:
Error message:
|
Failed again in: runtime-coreclr jitstress 20220128.1 Failed test:
Error message:
|
Failed again in: runtime-coreclr jitstress 20220312.2 Failed test:
Error message:
|
Failed again in: runtime-coreclr jitstress 20220319.1 Failed test:
Error message:
|
Failed again in: runtime-coreclr r2r-extra 20220327.1 Failed test:
Error message:
|
Recent failures have all been win-arm64 with the |
I've no idea. I don't recall moving it to Future at all. I was going through and adding "disabled-test", but setting the milestone and removing "triage" was a mistake. |
Tagging subscribers to this area: @dotnet/gc Issue DetailsRun: runtime-coreclr outerloop 20211007.5
Error message:
|
Failed again: runtime-coreclr outerloop 20230124.1 and many ohter outerloop runs Failed tests:
Error message:
Stack trace:
|
@AntonLapounov could you please take a look. This seems to be failing only on windows arm from what I can see. Has been intermittent but seems to be more consistent recently. |
@JulieLeeMSFT This issue has been tracking |
@AntonLapounov, the test is eventsourceerror but it is asserting with the same error message as test45929. I checked from last Thursday and you will see the eventsourceerror from all the outerloop runs since then.
|
@AntonLapounov, I checked 2 other runs again, and I see that they are all arm tests.
|
@JulieLeeMSFT Thank you. Could you please open a separate tracking issue for |
@AntonLapounov, I opened #81241.
|
Failed in Run: runtime-coreclr gcstress-extra 20230212.1 Failed tests:
Error message:
Stack trace:
|
The last case here is a duplicate of #81362, so I'm moving the description over there. This issue should only cover the test45929 test (which is currently disabled due to failure) |
Since the test is disabled, this is no longer "blocking". Removing "blocking" labels. |
Run: runtime-coreclr outerloop 20211007.5
Failed test:
Error message:
Report
Summary
The text was updated successfully, but these errors were encountered: