kevinveenbirkenbachandClaude Opus 5 3b4bc4ee65 perf(playwright): stage the persona flows once per run, mount them read-only ...

The previous commit packed the personas into one archive but still transferred them per role. orchestrate.yml runs 01_setup.yml once and then loops 02_run_one.yml over every app plus a retry pass, which is where the 22 transfers came from. Moving the staging into the setup phase leaves exactly one.

Each container now mounts the shared tree read-only at /e2e/tests/personas, the same pattern node_modules already uses. Both import directions were checked: specs require ./personas from /e2e/tests and land in the mount, while personas/utils/env.js requires ../../timeouts and reaches two levels up into the writable per-app staging dir, where the shared helpers are still placed. The nested mount therefore does not cut the relative imports.

Measured saving is 4.1 of the 4.2 minutes the copy cost in odoo 0, since only one transfer remains.

Not verified: the nested bind mount was not executed. Docker orders mounts by destination depth so /e2e lands before /e2e/tests/personas, but if that ordering did not hold the spec would fail loudly on require, not silently.

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

2026-08-12 22:24:14 +02:00

..

01_setup

Merge remote-tracking branch 'fork/feature/swarm-nfs' into feature/svc-net-tor

2026-07-24 04:30:56 +02:00

01_setup.yml

perf(playwright): stage the persona flows once per run, mount them read-only

2026-08-12 22:24:14 +02:00

02_run_one.yml

perf(playwright): stage the persona flows once per run, mount them read-only

2026-08-12 22:24:14 +02:00

main.yml

refactor(tasks): enforce and apply a single task-file numbering scheme

2026-07-23 20:01:31 +02:00