Skip to content

Disable VS Code extension E2E tests in CI - #18547

Merged
David Fowler (davidfowl) merged 1 commit into
mainfrom
disable-extension-e2e-tests
Jun 29, 2026
Merged

Disable VS Code extension E2E tests in CI#18547
David Fowler (davidfowl) merged 1 commit into
mainfrom
disable-extension-e2e-tests

Conversation

@JamesNK

Copy link
Copy Markdown
Member

Description

The VS Code extension E2E tests (specifically the Windows, debug-dashboard shard) are consistently failing on main, blocking unrelated PRs from merging.

This PR adds a false && guard to the extension_e2e_tests job condition and removes the corresponding gate skip-checks, following the same pattern as #18413.

Recent failures on main (last 5 days)

Date Run Commit Failing Job
Jun 28 CI #25637 Update OpenTelemetry.Instrumentation.StackExchangeRedis (#18532) VS Code extension E2E (Windows, debug-dashboard)
Jun 27 CI #25621 Prepare VS Code extension release v1.16.0 (#18528) VS Code extension E2E (Windows, debug-dashboard)
Jun 27 CI #25616 Fix VS Code extension CLI install (#18459) (#18522) VS Code extension E2E (Windows, debug-dashboard)
Jun 26 CI #25543 Make dashboard launch opt-in by default (#18361) VS Code extension E2E (Windows, debug-dashboard)

Tracked by #18412

The extension E2E shards (specifically Windows, debug-dashboard) are
consistently failing on main, blocking unrelated PRs from merging.

Recent failures on main (last 5 days):
- CI #25637 (Jun 28): Update OpenTelemetry.Instrumentation.StackExchangeRedis
- CI #25621 (Jun 27): Prepare VS Code extension release v1.16.0
- CI #25616 (Jun 27): Fix VS Code extension CLI install
- CI #25543 (Jun 26): Make dashboard launch opt-in by default

Adds a `false &&` guard to the extension_e2e_tests job condition and
removes the corresponding gate skip-checks, following the same pattern
as PR #18413.

Tracked by #18412.
Copilot AI review requested due to automatic review settings June 29, 2026 03:00
@github-actions

Copy link
Copy Markdown
Contributor

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 18547

Or

  • Run remotely in PowerShell:
iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 18547"

@JamesNK

Copy link
Copy Markdown
Member Author

cc Adam Ratzman (@adamint)

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR temporarily disables the consistently-failing VS Code extension E2E test job in CI so it stops blocking unrelated PRs from merging. It mirrors the approach used in #18413: the job is kept defined (so the aggregate gate's needs and the trigger-map binding test stay valid) but is forced to skip, and the gate is updated so the forced skip is not treated as a failure.

Changes:

  • Adds a false && guard to extension_e2e_tests.if so the job always skips, with a comment pointing to the tracking issue #18412 and flakiness issue #18098.
  • Removes the two aggregate-gate clauses (PR + non-PR) that treated a skipped extension_e2e_tests as a failure.
  • Updates the gate documentation to explain why the job is intentionally skipped.

@github-actions

Copy link
Copy Markdown
Contributor

Tests selector (audit mode)

The full test matrix and all jobs still run in audit mode. The tests and jobs below are what selective CI would run under enforcement.

Runs the full test matrix + all jobs (ALL) — a rule matching '.github/workflows/tests.yml' selects ALL


Selection computed for commit 99f2ede.

@github-actions

Copy link
Copy Markdown
Contributor

Retrying the failed CI jobs for this pull request from the CI run attempt. The rerun is being tracked in the rerun attempt.

@davidfowl
David Fowler (davidfowl) merged commit e6cd79e into main Jun 29, 2026
652 of 656 checks passed
@davidfowl
David Fowler (davidfowl) deleted the disable-extension-e2e-tests branch June 29, 2026 06:41
@github-actions github-actions Bot added this to the 13.5 milestone Jun 29, 2026
@aspire-repo-bot

Copy link
Copy Markdown
Contributor

✅ No documentation update needed.

docs_optional → build_or_ci_only

No documentation signals triggered (signal_count = 0). The sole changed file (.github/workflows/tests.yml) falls under .github/, matching the build_or_ci_only allowlist category. The PR adds a false && guard to the extension_e2e_tests CI job condition to disable failing VS Code extension E2E tests — a pure CI/build change with no user-facing behavior, API, or configuration impact.

@github-actions github-actions Bot locked and limited conversation to collaborators Jul 29, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants