fix(e2e): cycle gate resets games in place (no 240 page reloads) #103
Reference in New Issue
Block a user
Delete Branch "fix/cycle-gate-newgame"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The web-e2e cycle regression gate fails ~88% of runs with a 30s page.waitForFunction timeout at ~game 100/240 — a flaky-CI artifact of doing a fresh page.goto() per game (240 navigations in one browser context exhaust resources). The 18 actual e2e tests always pass; this is not a product bug.
Fix: add FERROUS_DEBUG.newGame(seed, drawThree) to game.js (already in play.html) and have cycle_metrics.js load the page once, then reset each game in place via newGame() instead of reloading. Evidence (progress 100/240 then timeout) directly supports the per-reload buildup cause.
Should finally turn web-e2e green.