Skip to content

Enable Chrome to run again on CI#46

Merged
frshwtr merged 2 commits intomasterfrom
fix-chrome-headless-ci
Jan 12, 2026
Merged

Enable Chrome to run again on CI#46
frshwtr merged 2 commits intomasterfrom
fix-chrome-headless-ci

Conversation

@andygout
Copy link
Contributor

Copy of alphagov/accessible-autocomplete#784 (from which this repo was originally forked) to enable CI workflow to start passing again as they are currently failing — see this failing GitHub CI workflow.

Quick fix for #781 that enables Chrome to run again on CI by using the --no-sandbox and --disable-sandbox-uuid flags.

This was something we used to do on alphagov/govuk-frontend and it gets the tests running again. However, we've since stopped using these flags so we should look at a more long term solution if it exists, as --no-sandbox is not problematic on CI (each CI run is in a container, which is its own little sandbox), but on our machines we should find a more secure way (although this is mitigated by the fact we only access our dev server)

Use the same `--no-sandbox` and `--disable-setuid-sandbox` flags
as on GOV.UK Frontend to enable Chrome to run on CI.
Similarly to Karma, Chrome won't launch on CI unless
the `--no-sandbox` and `--disable-setuid-sandbox` are set.
@andygout andygout requested a review from a team as a code owner January 10, 2026 17:15
@frshwtr frshwtr merged commit 919e875 into master Jan 12, 2026
5 checks passed
@frshwtr frshwtr deleted the fix-chrome-headless-ci branch January 12, 2026 15:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants