-
Notifications
You must be signed in to change notification settings - Fork 10k
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
Exit code 139 as part of RunTests.TestRunner.InstallAspNetAppIfNeededAsync #20219
Comments
Core dump available at https://dev.azure.com/dnceng/internal/_build/results?buildId=574320&view=ms.vss-test-web.build-test-results-tab&runId=18013826&resultId=120463&paneView=attachments Also, a previous failure of the same type: #19976 |
Was bored (nerd sniped?) and filed dotnet/runtime#34231 for this. |
Thanks for the investigation @BrennanConroy. Marking this as blocked until we can get a resolution from runtime. |
This is a runtime bug and not limited to |
Fix merged into runtime and now consumed by aspnet |
There test
Template_Produces_The_Right_Set_Of_FilesAsync(arguments: "new mvc -au MultiOrg --aad-instance https://login."..., expectedFiles: ["appsettings.Dev)
failed due to a 139 exit code.https://dev.azure.com/dnceng/internal/_build/results?buildId=574320&view=ms.vss-test-web.build-test-results-tab&runId=18013826&resultId=120446&paneView=debug
Need to investigate and quarantine it if necessary.
The text was updated successfully, but these errors were encountered: