Exit code 139 as part of RunTests.TestRunner.InstallAspNetAppIfNeededAsync
See original GitHub issue'/home/helixbot/work/A22508F7/w/BE2309D4/e/.dotnet18061/dotnet nuget list source' completed with exit code '139'
Exception in InstallAspNetAppIfNeeded: System.InvalidOperationException: Command /home/helixbot/work/A22508F7/w/BE2309D4/e/.dotnet18061/dotnet nuget list source returned exit code 139 output:
at RunTests.ProcessUtil.RunAsync(String filename, String arguments, String workingDirectory, Boolean throwOnError, IDictionary`2 environmentVariables, Action`1 outputDataReceived, Action`1 errorDataReceived, Action`1 onStart, CancellationToken cancellationToken) in /home/helixbot/work/A22508F7/w/BE2309D4/e/RunTests/ProcessUtil.cs:line 144
at RunTests.ProcessUtil.RunAsync(String filename, String arguments, String workingDirectory, Boolean throwOnError, IDictionary`2 environmentVariables, Action`1 outputDataReceived, Action`1 errorDataReceived, Action`1 onStart, CancellationToken cancellationToken) in /home/helixbot/work/A22508F7/w/BE2309D4/e/RunTests/ProcessUtil.cs:line 144
at RunTests.TestRunner.InstallAspNetAppIfNeededAsync() in /home/helixbot/work/A22508F7/w/BE2309D4/e/RunTests/TestRunner.cs:line 134
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.
Need to investigate and quarantine it if necessary.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Process finished with exit code 139 (interrupted by signal 11
I got this error in PHP, while running PHPUnit. The reason was a circular dependency. The error occurred on the following occasions:
Read more >Linux Segmentation Fault | Signal 11, Exit code 139
When a Docker container is terminated by a SIGSEGV signal, it throws exit code 139. This can indicate: An issue with application code...
Read more >How to debug Vivado crashes with exit code 139?
After hours vivado crashes with exit code 139 (indicating a Segmentation Fault which means that the program was trying to access a memory ......
Read more >Segmentation Fault in Linux Containers (Exit Code 139)
The exit code is reported as 139, indicating that a segmentation error caused the application inside the container to crash. Solving ...
Read more >Null failed (exit code 139) after migrating from V7 to V9
Hi all, I have impossibility to display the flow of a project after migrating my dataiku from V7 to V9. I have doubts...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This is a runtime bug and not limited to
InstallAspNetAppIfNeededAsync
, it’s mostly just tracking the issue so build ops folks who see the problem have an issue to link to.Fix merged into runtime and now consumed by aspnet