-
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 in JIT/superpmi/superpmicollect/superpmicollect.sh #53321
Comments
@sandreenko Can you please investigate this macOS/arm64 JitStress issue? |
SuperPMI is complaining about GetIntrinsicID, so maybe #52156 is at fault? |
Maybe due to #53440? |
I'm going to close this. |
it is probably still disabled by #53661 |
Your comment #53661 (comment) made me think we weren't going to do anything about it. Certainly, if we "scrub" the test exclusion list and see this exclusion, we can again decide to do something. Basically, I want to close all the "Test failure in... superpmicollect" issues because I think new and different failures are not getting opened as a result. If there's work to do, we should probably open a new/different issue specifically covering that work. |
I see, maybe it would be useful to:
|
Failure in macOS arm64, many JitStress modes
https://dev.azure.com/dnceng/public/_build/results?buildId=1156796&view=ms.vss-test-web.build-test-results-tab
(and the related JitStress2 jobs: https://dev.azure.com/dnceng/public/_build/results?buildId=1158176&view=ms.vss-test-web.build-test-results-tab)
First reported here: #32730 (comment)
The text was updated successfully, but these errors were encountered: