[CI Failure] VS Code extension E2E tests fail to download aspire-extension VSIX artifact after upstream packaging job failed #19744

Activity

1. github-actions

   added

   ci-failure-cause

   on Aug 27, 2026
2. Adam Ratzman (adamint)

   added

   area-vscode

   on Aug 27, 2026
3. radical commented on Aug 29, 2026

   

   Ankit Jain (radical)

   on Aug 29, 2026

   Member

   More actions

   [automated] The CI shepherd is watching this failure.

   Current assessment: Watch this single-infrastructure-occurrence for recurrence or positive recovery.

   Evidence reviewed:

   • issue:19744
   • run:33086828076
   • pr:19730

   Evidence still needed:

   • verified-fix-or-current-recurrence-check

   Reassess when: After another independent occurrence or positive recovery.

   No quarantine, retry, closure, or investigation has been started.
4. ellahathaway commented on Sep 22, 2026

   

   Ella Hathaway (ellahathaway)

   on Sep 22, 2026

   Contributor

   More actions

   This doesn’t appear to be an active failure now. Since September 8, I checked 109 main CI runs containing 100 extension producer-job executions. Of those, 97 succeeded; the other three failed unit tests but still published the VSIX—including [today’s run](https://github.com/microsoft/aspire/actions/runs/35683878838/job/106606877615). I found no recurrence of the reported packaging-failure cascade.

   However, the underlying workflow gap remains: current main still allows E2E to start without verifying that packaging produced the artifact. So, the transient incident has recovered, but it hasn’t been fixed structurally. I’m treating this as low-priority CI hardening rather than an active blocker/failure.