Dragan Spiridonov 2d35843ce8 fix(ci): wrap Vibium's Chrome to force --no-sandbox on GitHub runners ...

Diagnostic output from commit a4cb96c5 confirmed the residual error
is chromedriver's classic "HTTP 500 create session" — Chrome's
setuid sandbox can't initialize in the GitHub Actions runner
environment (no user namespaces, restricted proc).

Fix: after `vibium install` lays down Chrome for Testing into
~/.cache/vibium/chrome-for-testing/<version>/chrome, replace the
binary with a tiny bash wrapper that execs the real Chrome with
--no-sandbox --disable-dev-shm-usage appended. The wrapper lives
inside the ephemeral runner cache; nothing is shipped to users.

This is the standard workaround used by every Chromium-based CI
runner (Puppeteer, Playwright, chromedp all do the equivalent).

Also removed the diagnostic step added in a4cb96c5 (job green is
the signal now).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-04-22 11:43:27 +00:00

..

actions

feat: CI/CD best-in-class Phase 1+2 with crypto-secure randomness

2026-02-26 18:38:00 +00:00

ISSUE_TEMPLATE

feat: Complete Agentic QE Fleet v2.1 implementation (closes #101)

2025-12-02 15:02:30 +00:00

workflows

fix(ci): wrap Vibium's Chrome to force --no-sandbox on GitHub runners

2026-04-22 11:43:27 +00:00

FUNDING.yml

chore: add FUNDING.yml for GitHub sponsor badge

2025-12-04 15:19:09 +00:00

PULL_REQUEST_TEMPLATE.md

fix(init): release-gate corpus + --json contract (#401)

2026-04-07 16:44:27 +00:00