[Failing test]: Aspire.Cli.EndToEnd.Tests.SelfUpdateChannelPersistenceTests.SelfUpdateToStaging\_RelaunchedCliUsesStagingForImplicitProjectUpdate

[mitchdenny]

Build information

Build: https://github.com/microsoft/aspire/actions/runs/32950231041/attempts/5
Build error leg or test failing: Aspire.Cli.EndToEnd.Tests.SelfUpdateChannelPersistenceTests.SelfUpdateToStaging_RelaunchedCliUsesStagingForImplicitProjectUpdate
Logs: Tests / Cli.EndToEnd-SelfUpdateChannelPersistenceTests / Cli.EndToEnd-SelfUpdateChannelPersistenceTests (ubuntu-latest)
Artifact: All-TestResults

Fill in the error message template

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": "System.InvalidOperationException : Command failed with non-zero exit code (detected ERR prompt at sequence 16). Check the terminal recording for details.",
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Error details

Error Message: System.InvalidOperationException : Command failed with non-zero exit code (detected ERR prompt at sequence 16). Check the terminal recording for details.
Stack Trace:
   at Aspire.Tests.Shared.Hex1bAutomatorTestHelpers.WaitForSuccessPromptAsync(Hex1bTerminalAutomator auto, SequenceCounter counter, Nullable`1 timeout) in /_/tests/Shared/Hex1bAutomatorTestHelpers.cs:line 256
   at Aspire.Tests.Shared.Hex1bAutomatorTestHelpers.RunCommandAsync(Hex1bTerminalAutomator auto, String command, SequenceCounter counter, Nullable`1 timeout) in /_/tests/Shared/Hex1bAutomatorTestHelpers.cs:line 274
   at Aspire.Cli.EndToEnd.Tests.SelfUpdateChannelPersistenceTests.SelfUpdateToStaging_RelaunchedCliUsesStagingForImplicitProjectUpdate() in /_/tests/Aspire.Cli.EndToEnd.Tests/SelfUpdateChannelPersistenceTests.cs:line 81
   at Aspire.Cli.EndToEnd.Tests.SelfUpdateChannelPersistenceTests.SelfUpdateToStaging_RelaunchedCliUsesStagingForImplicitProjectUpdate() in /_/tests/Aspire.Cli.EndToEnd.Tests/SelfUpdateChannelPersistenceTests.cs:line 87
--- End of stack trace from previous location ---

Standard Output

CLI install strategy detection starting...
  → Selected: LocalArchive (ASPIRE_E2E_CLI_ARCHIVE_DIR=/home/runner/work/aspire/aspire/cli-archives)
Temporary workspace created at: /tmp/Aspire.Cli.EndToEnd.Tests/Workspace/gdbkrwnh.kem
Creating Docker test terminal:
  Test name:      SelfUpdateToStaging_RelaunchedCliUsesStagingForImplicitProjectUpdate
  Strategy:       LocalArchive (/home/runner/work/aspire/aspire/cli-archives) [expected=13.6.0-pr.18699.gc8ae846b]
  Expected ver:   13.6.0-pr.18699.gc8ae846b
  Variant:        DotNet
  Dockerfile:     (prebuilt image)
  Image:          aspire-cli-e2e-dotnet:prebuilt
  Workspace:      /tmp/Aspire.Cli.EndToEnd.Tests/Workspace/gdbkrwnh.kem
  Docker socket:  False
  Dimensions:     160x48
  Recording:      /home/runner/work/aspire/aspire/testresults/recordings/SelfUpdateToStaging_RelaunchedCliUsesStagingForImplicitProjectUpdate.cast
[TerminalRun] Captured diagnostics to: /home/runner/work/aspire/aspire/testresults/workspaces/SelfUpdateToStaging_RelaunchedCliUsesStagingForImplicitProjectUpdate
[TerminalRun]   Source workspace: /tmp/Aspire.Cli.EndToEnd.Tests/Workspace/gdbkrwnh.kem
[TerminalRun]   logs/: 2 file(s)

[joperezr]

🤖 Aspire triage pass — 2026-08-26 10:47 UTC

Area: area-cli
Kind: test-failure (likely flaky e2e — Hex1b terminal "ERR prompt at sequence 16")
Repro: partial — CI build, logs, and terminal recording linked in the issue body (no local minimal repro)
Affected version(s): CI build 13.6.0-pr.18699 (PR validation leg); test added by #19469
Severity: S3 — a CLI end-to-end test is failing; no customer-facing scenario broken and no product regression evidenced

Urgency: ⚪ backlog — no milestone
Reason: failing/flaky CLI e2e test, not a product regression or S1/S2 customer bug; no open 13.4.x/13.5 milestone and this does not clear the raised 13.6/13.5.x bar

Suggested owner(s): Sébastien Ros (@sebastienros) (backup James Newton-King (@JamesNK))
Evidence:

• SelfUpdateChannelPersistenceTests was introduced by Persist CLI channel across installs and self-updates #19469 (self-update channel persistence); its author is the issue reporter and is excluded per triage rules
• CODEOWNERS lists Sébastien Ros (@sebastienros) (with the reporter) for /src/Aspire.Cli/**
• Sébastien Ros (@sebastienros) recent area-cli merged PRs: Run CLI smoke tests across all PR platforms #19516, Sync ASP.NET Core certificate generation sources #19320, Honor ASPIRE_HOME for deployment state #19244; closed area-cli issues TypeScript AppHost fails code generation with 13.4.3 CLI and 13.5 daily SDK #18110, Make CLI NuGet metadata prefetching opt-in per command #18965
• James Newton-King (@JamesNK) is the highest-volume recent area-cli contributor/closer (e.g. Remove flaky duplicate child log path test #19538, Color statuses in aspire ps output #19369, Preserve CLI status messages without interactive spinners #19272; closed [13.5] Trace logging on aspire doctor causes weird indentation #19017, [main] aspire doctor taking 15 secs to run #19016, Use resolved dotnet paths in aspire doctor #19003)

Confidence: medium
Needs human?: no

[joperezr]

Mitch Denny (@mitchdenny) I dug into the current failures. All five retries on PR #19709 self-update to staging 13.5.3+b5f143315ffb6968ea939a9978797a5b20e4c688, then the implicit project update rewrites the AppHost to Aspire.AppHost.Sdk@13.5.3 and maps Aspire* exclusively to darc-pub-microsoft-aspire-b5f14331. That feed currently has no Aspire.AppHost.Sdk, while version 13.5.3 is available on NuGet.org, so restore fails and the CLI exits with code 13. The same test is failing across multiple unrelated PRs.

My current hypothesis is that this staging build has now shipped/promoted as stable, and the old per-commit staging feed was emptied or retired. That would leave the persisted staging identity pointing at a feed that no longer contains its matching packages. Could you take a look?

[karolz-ms]

Mitch Denny (@mitchdenny) Jose Perez Rodriguez (@joperezr) I have a PR that should fix this #19727 Feel free to update/merge it as necessary; PRs are blocked by this currently.