Fix stack overflow tests to accept 800703E9 exit code too #65331
Conversation
Sometimes a process failing with stack overflow returns exit code 0x800703e9 (ERROR_STACK_OVERFLOW). This change updates the stack overflow test to accept that code too.
| Console.WriteLine($"Exit code: 0x{testProcess.ExitCode:X8}, expected 0x{expectedExitCode:X8}"); | ||
| string separator = string.Empty; | ||
| StringBuilder expectedListBuilder = new StringBuilder(); | ||
| Array.ForEach(expectedExitCodes, code => { |
There was a problem hiding this comment.
It's a test so I assume we don't care about code size
|
The installer test failure is unrelated to this change. It is a SIGSEGV crash, however there are no artifacts (logs, dumps) available for further analysis. |
|
@janvorli I'm not sure if this is some known issue but I will ask around. @MattGal do you know anything about it? As a workaround you can also get to the artifacts from the build page. I think this one relates to the failed test. |
|
I think the issue is that the tests do not run in Helix but directly on the build machine. That's why that tab says "Unable to load Helix data". We have an issue to improve the message here: https://github.com/dotnet/core-eng/issues/13862. |
|
@lpatalas thank you for the details! |
ghost
locked as resolved and limited conversation to collaborators
Sometimes a process failing with stack overflow returns exit code
0x800703e9 (ERROR_STACK_OVERFLOW). This change updates the stack
overflow test to accept that code too.