chore(ci): give the VS Code extension test container a larger /dev/shm MONGOSH-3410#2737
Open
nbbeeken wants to merge 1 commit into
Open
chore(ci): give the VS Code extension test container a larger /dev/shm MONGOSH-3410#2737nbbeeken wants to merge 1 commit into
nbbeeken wants to merge 1 commit into
Conversation
The VS Code extension tests run a headless Chromium inside the ubuntu24.04-xvfb container. Docker's default 64MB /dev/shm is too small for the renderer, which intermittently crashes (renderer process exits with code 133) partway through the suite. Run the container with --shm-size=2g. Extracted from #2736 as part of splitting that branch into focused PRs.
Contributor
There was a problem hiding this comment.
Pull request overview
Updates Evergreen CI configuration to run the VS Code extension integration tests’ Docker container with a larger shared memory segment to prevent intermittent headless Chromium renderer crashes.
Changes:
- Add
--shm-size=2gto thedocker runinvocation used by thetest_vscodefunction. - Add an inline comment documenting the Chromium
/dev/shmcrash rationale. - Apply the same update to both the Evergreen template and the generated Evergreen config.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
.evergreen/evergreen.yml.in |
Adds --shm-size=2g to the VS Code test container run command and documents the reason. |
.evergreen.yml |
Regenerated config mirroring the same --shm-size=2g update for CI execution. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
nbbeeken
changed the title
nbbeeken
changed the title
nbbeeken
changed the title
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What
Run the VS Code extension test container with
--shm-size=2g.Why
The VS Code extension tests drive a headless Chromium inside the
ubuntu24.04-xvfbcontainer. Docker's default/dev/shmis only 64MB, which is too small for the Chromium renderer — it intermittently crashes (renderer process exits with code 133) partway through the suite, failingtest_vscodeeven though the mongosh tests themselves were passing.Giving the container a 2g
/dev/shmremoves that crash.Notes
.evergreen/evergreen.yml.inand regenerated.evergreen.yml(npm run update-evergreen-config); the two changes are identical.