-
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/stackoverflow/stackoverflowtester/stackoverflowtester.cmd #108215
Comments
@janvorli PTAL. |
Related to #106742. |
This appears to be different form #106742. The output
has an
so I think the question is whether the output interleaving is allowed and then either the output or the test should be fixed. |
The interleaving occurs only with superpmi due to its hooking into the sigsegv handler and the possibility that we hit it without the current thread being registered with the superpmi's PAL. I think that it would actually be better to not to run this test with superpmi at all. |
@BruceForstall, can you plz remove this test from spmi? |
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch |
It should be _extremely_ rare to need to disable a test during SuperPMI collection. However, one case was found, so introduce the ability to do so. Use `<SuperPmiCollectIncompatible>true</SuperPmiCollectIncompatible>` in a test project file. (which also requires `<RequiresProcessIsolation>true</RequiresProcessIsolation>`) Fixes dotnet#108215
…otnet#108873) It should be _extremely_ rare to need to disable a test during SuperPMI collection. However, one case was found, so introduce the ability to do so. Use `<SuperPmiCollectIncompatible>true</SuperPmiCollectIncompatible>` in a test project file. (which also requires `<RequiresProcessIsolation>true</RequiresProcessIsolation>`) Fixes dotnet#108215
Pipeline: runtime-coreclr superpmi-collect/20240922.1
Failed test:
Error Message:
Stack trace:
The text was updated successfully, but these errors were encountered: