-
Notifications
You must be signed in to change notification settings - Fork 5k
Test failure: baseservices/exceptions/stackoverflow/stackoverflowtester/stackoverflowtester.cmd #110173
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
Comments
Failed in: runtime-coreclr outerloop 20241127.3 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr outerloop 20241202.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr outerloop 20241203.2 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr outerloop 20241204.3 Failed tests:
Error message:
Stack trace:
|
This issue is also affecting optional pipelines: |
CC @mangod9. |
Failed in: runtime-coreclr pgostress 20241206.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr r2r-extra 20241208.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr pgo 20241211.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr outerloop 20241212.3 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr pgo 20241215.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr r2r 20241216.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr outerloop 20241219.3 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr jitstressregs 20241221.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr r2r-extra 20241222.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr outerloop 20241224.3 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr pgo 20241225.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr crossgen2 20241225.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr pgostress 20241227.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr outerloop 20241230.3 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr outerloop 20250401.2 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr outerloop 20250402.3 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr outerloop 20250406.3 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr outerloop 20250408.8 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr outerloop 20250412.3 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr outerloop 20250414.9 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr outerloop 20250416.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr outerloop 20250417.2 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr outerloop 20250419.2 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr crossgen2 20250420.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr jitstress 20250421.1 Failed tests:
Error message:
Stack trace:
|
@BruceForstall I am worried that if we disable the test, we will never figure out what's wrong. It never repros for me locally and even trying to run the legs manually in the lab didn't hit the problem for me. I have just created PR #114956 that enlarges the special stack we use for handling stack overflow, as the only explanation I have is that somehow it overflows in rare cases, maybe due to an async signal hitting the thread. |
Failed in: runtime-coreclr outerloop 20250424.3 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr outerloop 20250427.2 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr r2r-extra 20250427.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr outerloop 20250429.4 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr outerloop 20250505.2 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr outerloop 20250506.5 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr outerloop 20250507.2 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr r2r-extra 20250510.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr outerloop 20250512.5 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr outerloop 20250514.2 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr outerloop 20250519.4 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr outerloop 20250522.6 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr outerloop 20250526.4 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr outerloop 20250527.7 Failed tests:
Error message:
Stack trace:
|
Uh oh!
There was an error while loading. Please reload this page.
Failed in: runtime-coreclr outerloop 20241125.3
Failed tests:
Error message:
Stack trace:
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=878786
Error message validated:
[baseservices/exceptions/baseservices-exceptions/../stackoverflow/stackoverflowtester/stackoverflowtester.sh Timed Out (timeout in milliseconds: 600000 from variable __TestTimeout
]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 12/4/2024 10:05:14 PM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: