Skip to content
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

[rel/17.10] Update dependencies from dotnet/arcade #5090

Update dependencies from https://github.com/dotnet/arcade build 20240…

53b9806
Select commit
Loading
Failed to load commit list.
Closed

[rel/17.10] Update dependencies from dotnet/arcade #5090

Update dependencies from https://github.com/dotnet/arcade build 20240…
53b9806
Select commit
Loading
Failed to load commit list.
Azure Pipelines / microsoft.vstest failed Jul 1, 2024 in 18m 28s

Build #20240701.6 failed

Annotations

Check failure on line 13 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / microsoft.vstest

Build log #L13

(NETCORE_ENGINEERING_TELEMETRY=InitializeToolset) HTTP Error 500.30 - ASP.NET Core app failed to start 
Common solutions to this issue: 
The app failed to start
The app started but then stopped
The app started but threw an exception during startup
Troubleshooting steps: 
Check the system event log for error messages 
Enable logging the application process' stdout messages 
Attach a debugger to the application process and inspect 
For more guidance on diagnosing and handling these errors, visit Troubleshoot ASP.NET Core on Azure App Service and IIS. 

Check failure on line 25 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / microsoft.vstest

Build log #L25

(NETCORE_ENGINEERING_TELEMETRY=InitializeToolset) HTTP Error 500.30 - ASP.NET Core app failed to start 
Common solutions to this issue: 
The app failed to start
The app started but then stopped
The app started but threw an exception during startup
Troubleshooting steps: 
Check the system event log for error messages 
Enable logging the application process' stdout messages 
Attach a debugger to the application process and inspect 
For more guidance on diagnosing and handling these errors, visit Troubleshoot ASP.NET Core on Azure App Service and IIS. 

Check failure on line 37 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / microsoft.vstest

Build log #L37

(NETCORE_ENGINEERING_TELEMETRY=InitializeToolset) HTTP Error 500.30 - ASP.NET Core app failed to start 
Common solutions to this issue: 
The app failed to start
The app started but then stopped
The app started but threw an exception during startup
Troubleshooting steps: 
Check the system event log for error messages 
Enable logging the application process' stdout messages 
Attach a debugger to the application process and inspect 
For more guidance on diagnosing and handling these errors, visit Troubleshoot ASP.NET Core on Azure App Service and IIS. 

Check failure on line 49 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / microsoft.vstest

Build log #L49

(NETCORE_ENGINEERING_TELEMETRY=InitializeToolset) HTTP Error 500.30 - ASP.NET Core app failed to start 
Common solutions to this issue: 
The app failed to start
The app started but then stopped
The app started but threw an exception during startup
Troubleshooting steps: 
Check the system event log for error messages 
Enable logging the application process' stdout messages 
Attach a debugger to the application process and inspect 
For more guidance on diagnosing and handling these errors, visit Troubleshoot ASP.NET Core on Azure App Service and IIS.