From f9ba9a87d7fd10bb12033cb4b68c9047b9aada8f Mon Sep 17 00:00:00 2001 From: Logan Date: Wed, 19 Aug 2026 20:44:16 -0400 Subject: [PATCH] docs: note that CI's two engines share one app Which is why a shared-selector fault can be green on chromium and red on webkit in the same run, and how to reproduce it locally. --- .planning/NOTES.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/.planning/NOTES.md b/.planning/NOTES.md index 3c0fa9c..ee3cd36 100644 --- a/.planning/NOTES.md +++ b/.planning/NOTES.md @@ -3751,3 +3751,13 @@ class names into every ancestor query. It also only appears in a suite that has *done* something — the sections are empty on a fresh app, so this cannot be reproduced by opening Settings and looking. + +**And it appears on the second engine, not the first.** CI runs +chromium then webkit against **one app**, so a spec that scans in the +chromium pass leaves a finished job the webkit pass then trips over. +Three specs used that selector; two failed locally and the third +(`failure-voice.spec.ts`) was green on chromium and red on webkit in +the same run. Reproducing it locally is running the suite twice against +one `make dev-headless` — which is worth doing for any change that +leaves state behind, since it is the only place a cross-engine order +dependency shows up.