-
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 baseservices/exceptions/simple/ParallelCrashMainThread/ParallelCrashMainThread.sh #80356
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. |
Run: runtime-coreclr gcstress-extra 20230204.1 Failed test:
Error message:
|
Failed in Run: runtime-coreclr gcstress-extra 20230212.1 Failed tests:
Error message:
Stack trace:
|
Some recent failures of ParallelCrash:
|
Since all recent failures have been GCStress, I'm marking it as such. The OSX failure hasn't happened in a while. |
Also, the |
…ress These are regularly failing in GCStress testing. Tracking: dotnet#80356
Dup? #80357 |
caused by #81387? |
@kunalspathak These tests are designed to crash -- that is considered success. Would #81387 intercept this crash and interfere with the test run? How would I test this when running locally? |
I don't think so. It is an added functionality on top of existing one that collects crashdumps. Ideally, for this test, the test would have verified that it crashed as expected and then return the ExitCode = 0, but that doesn't seem be happening and the test crashes before that and the test driver doesn't get ExitCode=0 but gets a crash dump which #81387 will use to create stack trace. Additionally, this functionality was added 2 weeks back, while this test seems to be failing since January. If it helps, here is the call stack that we got (through #81387) for x64. However, for Arm64, for some reason, we do not print the stack trace. @hoyosjs - isn't llvm-symbolizer installed on those boxes? Stack trace on x64
|
Now disabled under GCStress pending failure investigation. |
Failed again in: runtime-coreclr jitstress 20230917.1 Failed tests:
Error message:
Stack trace:
|
Failed again in: runtime-coreclr r2r-extra 20231015.1 Failed tests:
Error message:
Stack trace:
More failures
|
@BruceForstall - seems we didn't disable the test for all modes? They seem to be still failing - https://dev.azure.com/dnceng-public/public/_build/results?buildId=467989&view=ms.vss-test-web.build-test-results-tab&runId=10642174&resultId=143206&paneView=debug @mangod9 - any plans of investigating this sooner? this is high hit issue. |
never mind. This one turns out to be a different issue #94652 |
Failed in: runtime-coreclr outerloop 20240610.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr outerloop 20240721.3 Failed tests:
Error message:
Stack trace:
|
this looks similar to #105229. |
Failed in: runtime-coreclr outerloop 20241016.7 Failed tests:
Error message:
Stack trace:
|
Run: runtime-coreclr outerloop 20230107.2
Failed test:
Error message:
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: