[release/9.0-staging] Update SDK to 9.0.308 #121852
Closed
Build Analysis / Build Analysis
failed
Nov 20, 2025 in 0s
.NET Result Analysis
Details
Tip
To unconditionally bypass the build analysis check (turn it green), you can use the escape mechanism feature. The completion time may vary, potentially taking several minutes, depending on the build analysis workload at the moment.
⚠️ The following pipeline(s) will not be analyzed as has been explicited excluded from analysis
Build Failures
runtime / Build / wasi-wasm linux release MonoAOTOffsets / Build product
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌src/mono/mono.proj(321,5): error MSB3073: The command "curl -L -o wasi-sdk-24.0.tar.gz https://github.com/WebAssembly/wasi-sdk/releases/download/wasi-sdk-24/wasi-sdk-24.0-x86_64-linux.tar.gz && mkdir -p /__w/1/s/src/mono/wasi/wasi-sdk/ && tar --strip-components=1 -xzf wasi-sdk-24.0.tar.gz -C /__w/1/s/src/mono/wasi/wasi-sdk/ && cp /__w/1/s/src/mono/wasi//wasi-sdk-version.txt /__w/1/s/src/mono/wasi/wasi-sdk/wasi-sdk-version.txt" exited with code 2.
runtime / Build / browser-wasm linux Release LibraryTests / Build product
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌CSC(0,0): error CS9057: The analyzer assembly '/__w/1/s/.dotnet/sdk/9.0.308/Sdks/Microsoft.NET.Sdk.Razor/source-generators/Microsoft.CodeAnalysis.Razor.Compiler.dll' references version '4.14.0.0' of the compiler, which is newer than the currently running version '4.12.0.0'.
-
❌src/mono/nuget/Microsoft.NET.Sdk.WebAssembly.Pack/Microsoft.NET.Sdk.WebAssembly.Pack.pkgproj(22,5): error : Could not find WasmAppHost files in /__w/1/s/artifacts/bin/WasmAppHost/wasm/Release/
runtime / Build / browser-wasm windows Release LibraryTests / Build product
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌CSC(0,0): error CS9057: The analyzer assembly 'D:\a\_work\1\s\.dotnet\sdk\9.0.308\Sdks\Microsoft.NET.Sdk.Razor\source-generators\Microsoft.CodeAnalysis.Razor.Compiler.dll' references version '4.14.0.0' of the compiler, which is newer than the currently running version '4.12.0.0'.
-
❌src\mono\nuget\Microsoft.NET.Sdk.WebAssembly.Pack\Microsoft.NET.Sdk.WebAssembly.Pack.pkgproj(22,5): error : Could not find WasmAppHost files in D:\a\_work\1\s\artifacts\bin\WasmAppHost\wasm\Release\
10 other jobs are failing and were not displayed due to space limitations.
Builds with failures: [runtime]
Test Failures (7 tests failed)
🔹 [All failing tests from runtime]
- Data Driven SubResults
- Exception Message
System.IO.IOException : The specified network name is no longer available. : 'C:\Windows\Temp\#File_SymbolicLinks_ih41qbof.d12\ResolveLinkTarget_Succeeds_163_emsr7o3q.link'.
- Stack Trace
at System.IO.FileSystem.GetFinalLinkTarget(String linkPath, Boolean isDirectory) in /_/src/libraries/System.Private.CoreLib/src/System/IO/FileSystem.Windows.cs:line 697 at System.IO.FileSystem.ResolveLinkTarget(String linkPath, Boolean returnFinalTarget, Boolean isDirectory) in /_/src/libraries/System.Private.CoreLib/src/System/IO/FileSystem.Windows.cs:line 529 at System.IO.File.ResolveLinkTarget(String linkPath, Boolean returnFinalTarget) in /_/src/libraries/System.Private.CoreLib/src/System/IO/File.cs:line 1444 at System.IO.Tests.File_SymbolicLinks.ResolveLinkTarget(String linkPath, Boolean returnFinalTarget) in /_/src/libraries/System.Runtime/tests/System.IO.FileSystem.Tests/File/SymbolicLinks.cs:line 31 at System.IO.Tests.BaseSymbolicLinks_FileSystem.ResolveLinkTarget_Succeeds(String pathToTarget, Boolean returnFinalTarget) in /_/src/libraries/System.Runtime/tests/System.IO.FileSystem.Tests/Base/SymbolicLinks/BaseSymbolicLinks.FileSystem.cs:line 169 at InvokeStub_BaseSymbolicLinks_FileSystem.ResolveLinkTarget_Succeeds(Object, Span`1) at System.Reflection.MethodBaseInvoker.InvokeWithFewArgs(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) in /_/src/libraries/System.Private.CoreLib/src/System/Reflection/MethodBaseInvoker.cs:line 136
- Data Driven SubResults
- Exception Message
Microsoft.DotNet.RemoteExecutor.RemoteExecutionException : Exit code was 134 but it should have been 42
- Stack Trace
at Microsoft.DotNet.RemoteExecutor.RemoteInvokeHandle.Dispose(Boolean disposing) in /_/src/Microsoft.DotNet.RemoteExecutor/src/RemoteInvokeHandle.cs:line 242 at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state) in /_/src/libraries/System.Private.CoreLib/src/System/Threading/ExecutionContext.cs:line 264 --- End of stack trace from previous location --- at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state) in /_/src/libraries/System.Private.CoreLib/src/System/Threading/ExecutionContext.cs:line 289 at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread) in /_/src/libraries/System.Private.CoreLib/src/System/Threading/Tasks/Task.cs:line 2346 --- End of stack trace from previous location --- at Microsoft.DotNet.RemoteExecutor.RemoteExecutorExtensions.DisposeAsync(RemoteInvokeHandle handle) in /_/src/libraries/Common/tests/System/Net/RemoteExecutorExtensions.cs:line 24 at System.Net.Http.Tests.HttpWindowsProxyTest.HttpProxy_Local_Bypassed(String name, Boolean shouldBypass) in /_/src/libraries/System.Net.Http/tests/UnitTests/HttpWindowsProxyTest.cs:line 165 --- End of stack trace from previous location ---
❌ System.Net.Http.Tests.HttpWindowsProxyTest.HttpProxy_Local_Bypassed(name: \"http://[2607:f8B0:4005:80A::200E]/\", shouldBypass: True)
- Exception Message
Microsoft.DotNet.RemoteExecutor.RemoteExecutionException : Exit code was 134 but it should have been 42
- Stack Trace
at Microsoft.DotNet.RemoteExecutor.RemoteInvokeHandle.Dispose(Boolean disposing) in /_/src/Microsoft.DotNet.RemoteExecutor/src/RemoteInvokeHandle.cs:line 242 at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state) in /_/src/libraries/System.Private.CoreLib/src/System/Threading/ExecutionContext.cs:line 264 --- End of stack trace from previous location --- at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state) in /_/src/libraries/System.Private.CoreLib/src/System/Threading/ExecutionContext.cs:line 289 at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread) in /_/src/libraries/System.Private.CoreLib/src/System/Threading/Tasks/Task.cs:line 2346 --- End of stack trace from previous location --- at Microsoft.DotNet.RemoteExecutor.RemoteExecutorExtensions.DisposeAsync(RemoteInvokeHandle handle) in /_/src/libraries/Common/tests/System/Net/RemoteExecutorExtensions.cs:line 24 at System.Net.Http.Tests.HttpWindowsProxyTest.HttpProxy_Local_Bypassed(String name, Boolean shouldBypass) in /_/src/libraries/System.Net.Http/tests/UnitTests/HttpWindowsProxyTest.cs:line 165 --- End of stack trace from previous location ---
❌ System.Net.Http.Tests.HttpWindowsProxyTest.HttpProxy_Local_Bypassed(name: \"http://[2607:f8b0:4005:80a::200e]/\", shouldBypass: True)
- Exception Message
Microsoft.DotNet.RemoteExecutor.RemoteExecutionException : Exit code was 134 but it should have been 42
- Stack Trace
at Microsoft.DotNet.RemoteExecutor.RemoteInvokeHandle.Dispose(Boolean disposing) in /_/src/Microsoft.DotNet.RemoteExecutor/src/RemoteInvokeHandle.cs:line 242 at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state) in /_/src/libraries/System.Private.CoreLib/src/System/Threading/ExecutionContext.cs:line 264 --- End of stack trace from previous location --- at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state) in /_/src/libraries/System.Private.CoreLib/src/System/Threading/ExecutionContext.cs:line 289 at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread) in /_/src/libraries/System.Private.CoreLib/src/System/Threading/Tasks/Task.cs:line 2346 --- End of stack trace from previous location --- at Microsoft.DotNet.RemoteExecutor.RemoteExecutorExtensions.DisposeAsync(RemoteInvokeHandle handle) in /_/src/libraries/Common/tests/System/Net/RemoteExecutorExtensions.cs:line 24 at System.Net.Http.Tests.HttpWindowsProxyTest.HttpProxy_Local_Bypassed(String name, Boolean shouldBypass) in /_/src/libraries/System.Net.Http/tests/UnitTests/HttpWindowsProxyTest.cs:line 165 --- End of stack trace from previous location ---
❌ System.IO.Tests.File_SymbolicLinks.ResolveLinkTarget_Succeeds [Console] [Details] [Artifacts] [0.07% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
Failing Configuration
-
❌ System.IO.Tests.File_SymbolicLinks.ResolveLinkTarget_Succeeds(pathToTarget: \"\\\\\\\\LOCALHOST\\\\share\\\\path\", returnFinalTarget: True)
❌ System.Net.Http.Tests.HttpWindowsProxyTest.HttpProxy_Local_Bypassed [Console] [Details] [Artifacts] [0.57% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
Failing Configurations (2)
-
❌ System.Net.Http.Tests.HttpWindowsProxyTest.HttpProxy_Local_Bypassed(name: \"http://localhost/\", shouldBypass: True)
❌ System.Net.NetworkInformation.Functional.Tests.WorkItemExecution [Console] [Details] [Artifacts] [1.90% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
This is a helix work item crash with status: BadExit. To investigate look the [Console log] / navigate to [Helix Artifacts]
Failing Configurations (2)
❌ System.Net.Quic.Functional.Tests.WorkItemExecution [Console] [Details] [Artifacts] [2.52% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
This is a helix work item crash with status: BadExit. To investigate look the [Console log] / navigate to [Helix Artifacts]
Failing Configurations (2)
Loading