Skip to content

Fix handling of multiple responses messages #6627

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.

Sign up for GitHub

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

Merged
stephentoub merged 1 commit into from
Jul 18, 2025

Fix handling of multiple responses messages

e3f5254
Select commit
Loading
Failed to load commit list.
Merged

Fix handling of multiple responses messages #6627

Fix handling of multiple responses messages
e3f5254
Select commit
Loading
Failed to load commit list.
Azure Pipelines / extensions-ci succeeded Jul 18, 2025 in 25m 5s

Build #20250717.9 had test failures

1 errors / 3 warnings

Details

Tests

  • Failed: 2 (0.00%)
  • Passed: 43,835 (92.70%)
  • Other: 3,451 (7.30%)
  • Total: 47,288

Annotations

Check failure on line 9 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / extensions-ci

Build log #L9 

Writing comment failed

Check failure on line 1 in Microsoft.Extensions.Caching.Hybrid.Tests.UnreliableL2Tests.WriteFailureInvisible(writeBreak: AsynchronousYield, errorIds: [7])

See this annotation in the file changed.

@azure-pipelines azure-pipelines / extensions-ci

Microsoft.Extensions.Caching.Hybrid.Tests.UnreliableL2Tests.WriteFailureInvisible(writeBreak: AsynchronousYield, errorIds: [7]) 

Assert.Equal() Failure: Strings differ
           ↓ (pos 0)
Expected: "7"
Actual:   ""
Raw output 
   at Microsoft.Extensions.Caching.Hybrid.Tests.LogCollector.AssertErrors(Int32[] errorIds) in /mnt/vss/_work/1/s/test/Libraries/Microsoft.Extensions.Caching.Hybrid.Tests/LogCollector.cs:line 60
   at Microsoft.Extensions.Caching.Hybrid.Tests.UnreliableL2Tests.WriteFailureInvisible(BreakType writeBreak, Int32[] errorIds) in /mnt/vss/_work/1/s/test/Libraries/Microsoft.Extensions.Caching.Hybrid.Tests/UnreliableL2Tests.cs:line 49
--- End of stack trace from previous location ---

Check failure on line 1 in Microsoft.AspNetCore.Diagnostics.Logging.Test.AcceptanceTests.HttpRequestBuffering_DoesNotBufferDisabledOrOversizedLogs

See this annotation in the file changed.

@azure-pipelines azure-pipelines / extensions-ci

Microsoft.AspNetCore.Diagnostics.Logging.Test.AcceptanceTests.HttpRequestBuffering_DoesNotBufferDisabledOrOversizedLogs 

Assert.Equal() Failure: Values differ
Expected: 6
Actual:   7
Raw output 
   at Microsoft.AspNetCore.Diagnostics.Logging.Test.AcceptanceTests.<>c.<<HttpRequestBuffering_DoesNotBufferDisabledOrOversizedLogs>b__24_1>d.MoveNext() in /mnt/vss/_work/1/s/test/Libraries/Microsoft.AspNetCore.Diagnostics.Middleware.Tests/Logging/AcceptanceTests.cs:line 950
--- End of stack trace from previous location ---
   at Microsoft.AspNetCore.Diagnostics.Logging.Test.AcceptanceTests.RunAsync[TStartup](LogLevel level, Action`1 configure, Func`4 func) in /mnt/vss/_work/1/s/test/Libraries/Microsoft.AspNetCore.Diagnostics.Middleware.Tests/Logging/AcceptanceTests.cs:line 175
   at Microsoft.AspNetCore.Diagnostics.Logging.Test.AcceptanceTests.HttpRequestBuffering_DoesNotBufferDisabledOrOversizedLogs() in /mnt/vss/_work/1/s/test/Libraries/Microsoft.AspNetCore.Diagnostics.Middleware.Tests/Logging/AcceptanceTests.cs:line 898
--- End of stack trace from previous location ---
View more details on Azure Pipelines