Suppress Chrome sandbox and GPU errors in CI#7191
Open
Dmytro-Melnyshyn wants to merge 1 commit into
Open
Conversation
Dmytro-Melnyshyn
changed the title
Dmytro-Melnyshyn
force-pushed
the
fix/chrome-ci-error-logs
branch
from
f29d042 to
f6435ff
Compare
OHaimanov
approved these changes
May 29, 2026
Add --no-sandbox and --disable-gpu Chrome flags via before:browser:launch to eliminate permission and dri3 errors in containerized Jenkins agents. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
OHaimanov
force-pushed
the
fix/chrome-ci-error-logs
branch
from
f6435ff to
83093e1
Compare
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
2 participants
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.
Summary
Running
node scripts/report-portal/runFailedTests.js --launchName runNightlyCypressEurekaTestsshows the following errors in Jenkins container logs, which actually do not affect anything, but confuse people.Added a
before:browser:launchhandler that injects two Chrome flags when running in a Chromium-family browser:--no-sandbox— removes the sandbox that requires OOM-score adjustment privileges (fixes thezygote_host_impl_linux.ccerror)--disable-gpu— disables GPU hardware acceleration (fixes thegpu_memory_buffer_support_x11.cc/ dri3 error)These errors are caused by Chrome's sandbox requiring elevated OS privileges and GPU/X11 access that are unavailable in containerized CI agents.
The
before:browser:launchhandler is insidesetupAfterSpecChaining'sitemsFilePathguard — it only activates when running therunFailedTests.jsscript. Regular Cypress runs (local dev, CI pipelines that invoke Cypress directly) are unaffected.Here are args available for the Chromium-based browsers.