docs(ci): correct the calibrated step ranges

This commit is contained in:
pj committed 2026-08-14 11:05:07 +05:30
1 parent 3ce9455928
commit e591cdf6bf
1 file changed
+7 -3
+7 -3
View File
@@ -57,12 +57,16 @@ cross-origin isolation. Served without them the app loads a blank canvas and
every step observes an empty accessibility tree. every step observes an empty accessibility tree.
The seeds in the workflow are calibrated, not guessed. On an M-series mac, The seeds in the workflow are calibrated, not guessed. On an M-series mac,
android seed 3 finds the bug at step 110-116 (seeds 1, 2 and 4 run 120 steps android seed 3 finds the bug at step 95-116 (seeds 1, 2 and 4 run 120 steps
clean), ios seed 1 finds it at step 129-134, and web seed 1 finds it at step 109, clean), ios seed 1 finds it at step 130-134, and web seed 1 finds it at step
reproducing 3 runs out of 3. All three run against a 240-step budget. Keep the 105-109, each reproducing 3 runs out of 3. All three run against a 240-step budget. Keep the
web seed pinned: 9 of 12 random seeds found the bug within 200 steps, so an web seed pinned: 9 of 12 random seeds found the bug within 200 steps, so an
unpinned one would flake. unpinned one would flake.
Repeating the ios leg by hand is not the same as running it in CI: with
`--clear-data=false` a second local run inherits the first one's accounts, so
`simctl uninstall` before each repeat or the numbers drift.
The ios leg passes `--clear-data=false`, because the job installs a fresh build The ios leg passes `--clear-data=false`, because the job installs a fresh build
immediately before the run and a freshly installed app is already clear state. immediately before the run and a freshly installed app is already clear state.
The in-run reinstall is worth avoiding: `simctl uninstall` + `install` followed The in-run reinstall is worth avoiding: `simctl uninstall` + `install` followed