Skip to content

Update branding to 9.0.14

d71774d
Select commit
Loading
Failed to load commit list.
Merged

Update branding to 9.0.14 #65294

Update branding to 9.0.14
d71774d
Select commit
Loading
Failed to load commit list.
Build Analysis / Build Analysis failed Feb 2, 2026 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.

Known Infrastructure Errors

Build Failures

aspnetcore-ci / Build / Tests: Helix x64

[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]
    ❌The job running on agent NetCore-Svc-Public 147 ran longer than the maximum time of 240 minutes. For more information, see https://go.microsoft.com/fwlink/?linkid=2077134

aspnetcore-quarantined-pr / Tests: Helix

[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]
    ❌The job running on agent NetCore-Svc-Public 120 ran longer than the maximum time of 150 minutes. For more information, see https://go.microsoft.com/fwlink/?linkid=2077134

Known test errors

Test Failures (7 tests failed)

🔹 [All failing tests from aspnetcore-quarantined-pr]

    ⚠️ 3 failing tests not displayed for this pipeline due to space limitations

    Interop.FunctionalTests.Http2.Http2RequestTests.GET_RequestReturnsLargeData_GracefulShutdownDuringRequest_RequestGracefullyCompletes [Console] [Details] [Artifacts] [2.69% failure rate]
    [ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]

    Failing Configurations (3)

    Data Driven SubResults
      Interop.FunctionalTests.Http2.Http2RequestTests.GET_RequestReturnsLargeData_GracefulShutdownDuringRequest_RequestGracefullyCompletes(hasTrailers: False)
      Exception Message
      System.IO.IOException : The request was aborted.
      ---- System.IO.IOException : Unable to write data to the transport connection: Broken pipe.
      -------- System.Net.Sockets.SocketException : Broken pipe
      Stack Trace
         at System.Net.Http.Http2Connection.ThrowRequestAborted(Exception innerException)
         at System.Net.Http.Http2Connection.Http2Stream.CheckResponseBodyState()
         at System.Net.Http.Http2Connection.Http2Stream.TryReadFromBuffer(Span`1 buffer, Boolean partOfSyncRead)
         at System.Net.Http.Http2Connection.Http2Stream.ReadDataAsync(Memory`1 buffer, HttpResponseMessage responseMessage, CancellationToken cancellationToken)
         at Interop.FunctionalTests.Http2.Http2RequestTests.StartLongRunningRequestAsync(ILogger logger, IHost host, HttpMessageInvoker client) in /_/src/Servers/Kestrel/test/Interop.FunctionalTests/Http2/Http2RequestTests.cs:line 310
         at Microsoft.AspNetCore.InternalTesting.TaskExtensions.TimeoutAfter[T](Task`1 task, TimeSpan timeout, String filePath, Int32 lineNumber) in /_/src/Shared/TaskExtensions.cs:line 88
         at Interop.FunctionalTests.Http2.Http2RequestTests.GET_RequestReturnsLargeData_GracefulShutdownDuringRequest_RequestGracefullyCompletes(Boolean hasTrailers) in /_/src/Servers/Kestrel/test/Interop.FunctionalTests/Http2/Http2RequestTests.cs:line 280
      --- End of stack trace from previous location ---
      ----- Inner Stack Trace -----
         at System.Net.Http.Http2Connection.FlushOutgoingBytesAsync()
      ----- Inner Stack Trace -----
         at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.CreateException(SocketError error, Boolean forAsyncThrow)
         at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.SendAsyncForNetworkStream(Socket socket, CancellationToken cancellationToken)
         at System.Net.Sockets.Socket.SendAsyncForNetworkStream(ReadOnlyMemory`1 buffer, SocketFlags socketFlags, CancellationToken cancellationToken)
         at System.Net.Sockets.NetworkStream.WriteAsync(ReadOnlyMemory`1 buffer, CancellationToken cancellationToken)
         at System.Net.Http.Http2Connection.FlushOutgoingBytesAsync()
         at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine](TStateMachine& stateMachine)
         at System.Net.Http.Http2Connection.FlushOutgoingBytesAsync()
         at System.Net.Http.Http2Connection.ProcessOutgoingFramesAsync()
         at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.AsyncStateMachineBox`1.ExecutionContextCallback(Object s)
         at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
         at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.AsyncStateMachineBox`1.MoveNext(Thread threadPoolThread)
         at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.AsyncStateMachineBox`1.MoveNext()
         at System.Threading.ThreadPoolWorkQueue.Dispatch()
         at System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart()
         at System.Threading.Thread.StartCallback()
      --- End of stack trace from previous location ---
      
    Microsoft.AspNetCore.Hosting.HostingEventSourceTests.VerifyCountersFireWithCorrectValues [Console] [Details] [Artifacts] [0.88% failure rate]
    [ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]

    Failing Configuration

    Exception Message
    System.InvalidOperationException : Results ended with final value of 0. Expected value of 1.
    ---- System.Threading.Tasks.TaskCanceledException : A task was canceled.
    CallStack
       at System.Collections.Generic.AsyncEnumerableExtensions.WaitForValueAsync[T](IAsyncEnumerator`1 values, T expectedValue) in /_/src/Hosting/Hosting/test/Internal/AsyncEnumerableExtensions.cs:line 28
       at Microsoft.AspNetCore.Hosting.HostingEventSourceTests.VerifyCountersFireWithCorrectValues() in /_/src/Hosting/Hosting/test/Internal/HostingEventSourceTests.cs:line 212
    --- End of stack trace from previous location ---
    ----- Inner Stack Trace -----
       at System.Threading.Channels.ChannelReader`1.ReadAllAsync(CancellationToken cancellationToken)+MoveNext()
       at System.Threading.Channels.ChannelReader`1.ReadAllAsync(CancellationToken cancellationToken)+System.Threading.Tasks.Sources.IValueTaskSource<System.Boolean>.GetResult()
       at System.Collections.Generic.AsyncEnumerableExtensions.WaitForValueAsync[T](IAsyncEnumerator`1 values, T expectedValue) in /_/src/Hosting/Hosting/test/Internal/AsyncEnumerableExtensions.cs:line 15
    Microsoft.AspNetCore.InternalTesting.Tests.QuarantinedTestAttributeTest.FlakyTestToEnsureRetryWorks [Console] [Details] [Artifacts] [17.96% failure rate]
    [ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]

    Failing Configuration

    Exception Message
    Assert.True() Failure
    Expected: True
    Actual:   False
    CallStack
       at Microsoft.AspNetCore.InternalTesting.Tests.QuarantinedTestAttributeTest.FlakyTestToEnsureRetryWorks() in /_/src/Testing/test/QuarantinedTestAttributeTest.cs:line 27
       at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
       at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)
    Microsoft.AspNetCore.Server.HttpSys.FunctionalTests.DelegateTests.DelegateAfterReceiverRestart [Console] [Details] [Artifacts] [9.19% failure rate]
    [ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]

    Failing Configuration

    Exception Message
    System.Net.Http.HttpRequestException : Response status code does not indicate success: 500 (Internal Server Error).
    CallStack
       at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()
       at System.Net.Http.HttpClient.GetStringAsyncCore(HttpRequestMessage request, CancellationToken cancellationToken)
       at Microsoft.AspNetCore.Server.HttpSys.FunctionalTests.DelegateTests.SendRequestAsync(String uri) in /_/src/Servers/HttpSys/test/FunctionalTests/DelegateTests.cs:line 272
       at Microsoft.AspNetCore.Server.HttpSys.FunctionalTests.DelegateTests.DelegateAfterReceiverRestart() in /_/src/Servers/HttpSys/test/FunctionalTests/DelegateTests.cs:line 263
    --- End of stack trace from previous location ---

Was this helpful? Yes No