[CI Failure] SQL Server 2022 Testcontainer exits with code 1 via handle-crash.sh, breaking EF Core/SqlClient tests #20234
Copy link
Copy link
Open
Labels
Description
Build Information
Build: https://github.com/microsoft/aspire/actions/runs/35349639380
Build error leg: Tests / No-package tests (regular, Aspire.Microsoft.EntityFrameworkCore.SqlServer.Tests, Microsoft.Entity... / Microsoft.EntityFrameworkCore.SqlServer (ubuntu-latest)
Pull request: #20209
Classification Analysis
All 78 test failures in this job stem from the shared SqlServerContainerFixture class fixture throwing in InitializeAsync because the SQL Server 2022 Docker container exited with code 1 shortly after startup (invoking /opt/mssql/bin/handle-crash.sh). This is an infrastructure/container-runtime failure unrelated to the PR, which only modifies GitHub Actions workflow files (gh-aw agentic workflow modernization) and adds a workflow-script test file; none of the changed files touch SQL Server, EF Core, or SqlClient test code.
Failure Information
Job output snippet
Aspire.Microsoft.EntityFrameworkCore.SqlServer.Tests.EnrichSqlServerTests.ShouldThrowIfDbContextIsNotRegistered
Class fixture type 'Aspire.Microsoft.Data.SqlClient.Tests.SqlServerContainerFixture' threw in InitializeAsync
---- DotNet.Testcontainers.Containers.ContainerNotRunningException : Container 7a6233ae03adefccef53762835d3479f6baa3e39febaf99b4c2f5728216304dd exited with code 1.
Stdout:
2026-09-18T13:24:41.529162744Z SQL Server 2022 will run as non-root by default.
2026-09-18T13:24:41.529190227Z This container is running as user mssql.
2026-09-18T13:24:41.529193345Z To learn more visit https://go.microsoft.com/fwlink/?linkid=2099216.
2026-09-18T13:24:43.232366563Z Executing: /opt/mssql/bin/handle-crash.sh with parameters
handle-crash.sh
/opt/mssql/bin/sqlservr
27
/opt/mssql/bin
/var/opt/mssql/log/
Stack Trace:
----- Inner Stack Trace -----
at DotNet.Testcontainers.Containers.DockerContainer.ThrowIfContainerNotRunningAsync(WaitStrategyMode waitStrategyMode, Exception innerException) in /_/src/Testcontainers/Containers/DockerContainer.cs:line 737
at DotNet.Testcontainers.Containers.DockerContainer.CheckReadinessAsync(WaitStrategy waitStrategy, CancellationToken ct) in /_/src/Testcontainers/Containers/DockerContainer.cs:line 690
at DotNet.Testcontainers.Containers.DockerContainer.UnsafeStartAsync(CancellationToken ct) in /_/src/Testcontainers/Containers/DockerContainer.cs:line 557
at DotNet.Testcontainers.Containers.DockerContainer.StartAsync(CancellationToken ct) in /_/src/Testcontainers/Containers/DockerContainer.cs:line 340
at Aspire.Microsoft.Data.SqlClient.Tests.SqlServerContainerFixture.InitializeAsync() in /_/tests/Aspire.Microsoft.Data.SqlClient.Tests/SqlServerContainerFixture.cs:line 25
----- Inner Stack Trace -----
at Docker.DotNet.DockerClient.HandleIfErrorResponseAsync(HttpStatusCode statusCode, HttpResponseMessage response, IEnumerable`1 handlers) in /_/src/Docker.DotNet/DockerClient.cs:line 494
at Docker.DotNet.DockerClient.MakeRequestAsync[T](...)
This identical failure recurred across all 36 test cases in the EnrichSqlServerTests class within the same job, confirming a single shared-fixture infrastructure failure rather than 36 independent code-related regressions.
Description
SQL Server 2022 Testcontainer exits with code 1 via handle-crash.sh, breaking EF Core/SqlClient tests
Type: infra-failure
Occurrences
| Date | Build | Job | PR |
|---|---|---|---|
| 2026-09-18 | 35349639380 | Tests / No-package tests (regular, Aspire.Microsoft.EntityFrameworkCore.SqlServer.Tests, Microsoft.Entity... / Microsoft.EntityFrameworkCore.SqlServer (ubuntu-latest) | #20209 |
Activity
davidfowl commentedon Nov 1, 2026
Closure recommendation: no recurrence in 7 days of CI
ci.ymlattempt-1 runs (824 runs, 2026-10-25T10:57Z → 2026-11-01T09:51Z; every failed test-job log scanned)handle-crash.shMicrosoft.EntityFrameworkCore.SqlServer: main 126, PR 140 (Linux and Windows), 0 failuresMicrosoft.Data.SqlClient: main 126, PR 140, 0 failuresHosting.SqlServer: main 126, PR 302. There were 3 PR failures; none involve a container crash.handle-crash: 0I recommend closing this. Reopen it if the signature comes back.
🤖 Posted by AspireAgent (AI Agent)