[CI Failure] Flaky: SqlServerReplCommandTests fail because sqlserver container never becomes healthy
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- csharp, docker
- Domain
- infrastructure, testing
Research direction
Start with SqlServerReplCommandTests in the Aspire.Hosting.SqlServer.Tests project and inspect the container health and startup configuration used by ReplExecutesAuthenticatedBatch. Reproduce the failure by running the two observed test cases, then trace why the SQL Server container remains in the Starting state. Done when both cases reliably pass without the container health timeout.
Written by the indexing model from the issue text.
Description
Build Information
Build: https://github.com/microsoft/aspire/actions/runs/41932442823
Build error leg: Tests / No-package tests (regular, Aspire.Hosting.SqlServer.Tests, Hosting.SqlServer, Hosting.SqlServer, ... / Hosting.SqlServer (ubuntu-latest)
Error Message
System.OperationCanceledException : Resource 'sqlserver' failed to become healthy before the operation was cancelled.
- Current State: Starting
- Current Health: (null)
Description
Flaky: SqlServerReplCommandTests fail because sqlserver container never becomes healthy
Type: flaky-test
Observed tests
Aspire.Hosting.SqlServer.Tests.SqlServerReplCommandTests.ReplExecutesAuthenticatedBatch(configure: False)— job 126935434853 (Tests / No-package tests (regular, Aspire.Hosting.SqlServer.Tests, Hosting.SqlServer, Hosting.SqlServer, ... / Hosting.SqlServer (ubuntu-latest))Aspire.Hosting.SqlServer.Tests.SqlServerReplCommandTests.ReplExecutesAuthenticatedBatch(configure: True)— job 126935434853 (Tests / No-package tests (regular, Aspire.Hosting.SqlServer.Tests, Hosting.SqlServer, Hosting.SqlServer, ... / Hosting.SqlServer (ubuntu-latest))
Occurrences
Showing 1 most recent of 1 occurrences.
| Date | Build | Job | Context |
|---|---|---|---|
| 2026-11-05 | 41932442823 | Tests / No-package tests (regular, Aspire.Hosting.SqlServer.Tests, Hosting.SqlServer, Hosting.SqlServer, ... / Hosting.SqlServer (ubuntu-latest) |
main |
- Dominant language
- C#
- Stars
- 6.4k
- Forks
- 1k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 349
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/aspire
-
Aspire.Hosting.Yarp flattens TimeSpan cluster settings (ActivityTimeout, health-check intervals) into per-property env vars the YARP container ignoresPossibly taken @itsrayeedscodespace claimed this 1 day ago. Openarea-integrations
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Dashboard structured logs toolbar overlaps the resource name and wraps poorly in constrained layoutsOpenarea-dashboard
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
-
area-dashboard
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 2 days
-
area-dashboard
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 2 days
-
area-templates
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 2 days
All issues in microsoft/aspire
Similar issues
-
Assert.That on a null non-generic IEnumerable throws ArgumentNullException, so IsNull() cannot passOpenbug P2
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
area/automation area/sdk kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
unoplatform/uno.templates#2406 ·
Maintainers usually reply within 1 day
-
bug frontend ui
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
documentation trivial
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day