docs(e2e): note Claude Code sandbox blocks Chromium Mach-port IPC
Discovered while running Task 12's Playwright editor test: Chromium's bootstrap_check_in Mach-port rendezvous is blocked by the sandbox, which surfaces as a FATAL crash with "Permission denied (1100)" rather than a path-related error. Document the workaround so future agents running e2e tests in the same sandbox don't waste time debugging it as a Playwright/network issue. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
86fe564ff8
commit
7b54d1348b
1 changed files with 7 additions and 0 deletions
|
|
@ -109,3 +109,10 @@ uv run playwright install chromium
|
||||||
|
|
||||||
Run with `uv run pytest -m e2e`. Excluded from the default fast suite
|
Run with `uv run pytest -m e2e`. Excluded from the default fast suite
|
||||||
via the `e2e` marker.
|
via the `e2e` marker.
|
||||||
|
|
||||||
|
**Sandbox note:** Chromium needs Mach-port IPC on macOS, which the
|
||||||
|
Claude Code sandbox blocks. When running e2e tests from a sandboxed
|
||||||
|
agent session, pass `dangerouslyDisableSandbox: true` on the
|
||||||
|
`uv run pytest -m e2e` invocation (the symptom of a sandboxed run is
|
||||||
|
a `FATAL` Chromium crash with `Permission denied (1100)` on Mach port
|
||||||
|
rendezvous, not a missing-binary or network error).
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue