-
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
profiler\multiple test failed #100114
Comments
This is crashing in new EH:
|
@janvorli has this been fixed? |
@lewing I believe I have looked into the original and it was actually not an issue of the new EH, but rather a regular unhandled exception or something along these lines. Unfortunately, the only two remaining failures from the list above are misclassified, so I cannot double check it now. |
Either way, CI does not hit this anymore, so the issue can be closed. |
Failed again in https://dev.azure.com/dnceng-public/public/_build/results?buildId=655183&view=ms.vss-test-web.build-test-results-tab&runId=16217960&resultId=100465&paneView=debug with the same stacktrace as #100114 (comment) |
@jkotas the failure in the referenced run is just an unhandled exception. From the test log:
The last message from the actual test is
So that sounds like profiler or test related issue. |
Ah ok, I have not realized that this is the new callstack for unhandled exception. I agree that it looks like a profiler test issue. We would need a crash dump of the hung process to diagnose it. |
Tagging subscribers to this area: @tommcdon |
Based on the dump, the child process exit code is 0:
It suggests that the child process exited without crashing. The problem seems to be in the parsing of the child process output. |
Missing I would keep this issue open for 2 weeks. If we do not see any new hits in 2 weeks, we can declare it fixed. |
Failed in: runtime-coreclr r2r 20240429.1 Failed tests:
Error message:
Stack trace:
|
The latest failure doesn't make sense to me
The profilee returned code 100 which means that the |
A good question to ask is why this test and why arm64 only. It all points to bug(s) related to arm64 weaker memory model in the test code or in the code specifically exercised by this test. The missing |
I fixed another issue and added a speculative fix in #102066, for now I am going to wait to see if it fails again before investigating any further |
There have been no issues reported by automation since this issue has been fixed, closing as "fixed" |
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=655183
Build error leg or test failing: profiler\multiple\multiple\multiple.cmd
Pull request: #101291
Error Message
Fill the error message using step by step known issues guidance.
Known issue validation
Build: 🔎⚠️ Validation could not be done without an Azure DevOps build URL on the issue. Please add it to the "Build: 🔎" line.
Result validation:
Validation performed at: 4/25/2024 9:12:24 PM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: