Skip to content

Run the Chromium build check against the image's browsers - #93

Merged
splitbrain merged 1 commit into
splitbrain:mainfrom
splitbrain-bot:claude/test-stage-chromium-path
Oct 4, 2026
Merged

splitbrain merged 1 commit into
splitbrain:mainfrom
splitbrain-bot:claude/test-stage-chromium-path

Conversation

@splitbrain-bot

Copy link
Copy Markdown

Fixes the box image build on main, which failed in 37196603548 after #92.

Cause

#92 moved ENV PLAYWRIGHT_BROWSERS_PATH=/home/agent/.cache/ms-playwright to before the checks. The Chromium check (playwright-cli open) used to run while that variable still pointed at the image's browsers in /opt/playwright. Now it looked in the home:

Browser "chromium" is not installed; expected executable at /home/agent/.cache/ms-playwright/chromium_headless_shell-1247/...

At runtime the entrypoint links the image's builds into that path. During the build, nothing does.

Fix

The Chromium check sets PLAYWRIGHT_BROWSERS_PATH to $BOXES_IMAGE_BROWSERS for its own step, which is the value it ran with before #92.

The other checks depend on the moved variable as intended. The Firefox and WebKit check downloads into the home path. The symlink check sets its own path.

Testing

I cannot run containers on my machine, so this build is the first test of the fix.

Commit 8386f98 set the runtime PLAYWRIGHT_BROWSERS_PATH before the checks.
The Chromium check then looked for its browser in the home, where only the
entrypoint links the image's builds, and the box image build failed. The
check now uses the image's browser directory, as it did before that commit.
@splitbrain
splitbrain merged commit 5e49380 into splitbrain:main Oct 4, 2026
9 checks passed
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