Uh oh!
There was an error while loading. Please reload this page.
ci: disable MongoDB/Redis community-world E2E on stable - #2188
Closed
VaguelySerious wants to merge 1 commit into
Closed
ci: disable MongoDB/Redis community-world E2E on stable#2188VaguelySerious wants to merge 1 commit into
VaguelySerious wants to merge 1 commit into
Conversation
These jobs have hung until the 30-minute timeout on every stable run since #1963 removed the workbench world-kickstart (`getWorld().start()`), which the community world adapters rely on to dispatch runs. They were also part of the required E2E check, so every stable PR/push failed the gate after wasting ~30 minutes per runner. Disable the community matrix + jobs and drop them from the required check to stop the bleeding. A follow-up PR will restore the kickstart in the community E2E lane and add a fast-fail preflight so they provide real signal again without being able to hang. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
🦋 Changeset detectedLatest commit: e37b27e The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
🧪 E2E Test Results✅ All tests passed Summary
Details by Category✅ ▲ Vercel Production
✅ 💻 Local Development
✅ 📦 Local Production
✅ 🐘 Local Postgres
✅ 🪟 Windows
✅ 📋 Other
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
E2E Community World (MongoDB)andE2E Community World (Redis)hang until the 30-minute job timeout on everystablerun, and they are part of the requiredE2E Required Check— so every stable PR/push fails the gate after burning ~30 min × 2 runners.Root cause (when & what)
Bisected across stable runs: last green was
a350e8ddf(2026-05-18 22:00 UTC), first timeout was the very next commit4bc53fc7a— "Remove instrumentation from workbench (#1959) (#1963)" (2026-05-18 22:01 UTC).That commit deleted
workbench/nextjs-turbopack/instrumentation.ts, whose only payload was the world kickstart:The MongoDB/Redis community adapters dispatch created runs via an in-process queue worker that only runs if
getWorld().start()is called. With the stub gone, every run stayspendingatrun_created; eache2e.test.tscase waits its full ~60s timeout, and 25+ sequential cases blow pasttimeout-minutes: 30. Other lanes (vercel/local/postgres) are unaffected — they don't depend on that side effect, and Turso (no service container) still passes.This PR (stop the bleeding)
if: falseongetCommunityWorldsMatrix+e2e-community(no more 30-min waste).e2e-communityfrome2e-required-checkso the gate stops failing.summaryis untouched (it already treats community as a non-blocking warning and handles the skipped status fine).Follow-up
A separate PR will restore the world kickstart in the community E2E lane only (keeping the shipped workbench aligned with the getting-started docs, per #1959's intent) and add a fast-fail preflight + lower timeout, so these jobs provide real signal again and can never silently hang for 30 minutes.
🤖 Generated with Claude Code