Browser spec "another step opens at its own tail" fails now and then under the full lane #193
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
ui/e2e/ui-polish-103.spec.ts:106, "another step opens at its own tail, however far up the last one was read", failed once in the full lane on61f84b0(2026-10-18):After Escape closes the second step, the "jump to latest" button is still there 10 s later. The merge under test changed no transcript or scroll code (one Settings label only).
Since then:
--repeat-each 8 --workers 4);So it fails only under the full lane's load, which points at a race between the step closing and the transcript's follow state, not at a timeout to raise. Worth finding: the same family of "flake" (the keyboard specs, 2026-10-16) turned out to be a real race in the console's route handling.
To do
--repeat-eachwith more workers than cores) and read what keeps[data-jump-latest]after Escape.Two more specs that fail only under load, seen 2026-10-18 while other test lanes ran on the same laptop (load average 12-49):
e2e/follow-transition.spec.ts:547"the stage › a click on a script output's fold during the arrival folds it":[data-transcript] button[aria-expanded] is not on the page. Failed once in a full lane on1330513, once in a fast lane onef05d28(a tree without the top-bar change), and 1 of 5 in--repeat-each 5 --workers 3. It passes on its own and in quieter lanes. The fold button is looked for while the stage's arrival transition is still running, so it may not be there yet.e2e/keyboard.spec.ts:35"the go-to sequences reach every page":g i → inboxreadrunsafter 10 s, once in that full lane. Then 5 of 5 passed on their own. The same spec was fixed for a real route race inaa31a26, so worth checking it is only load this time.All three in this issue share a shape: a spec waits on a moment of an animation or a route change that a loaded machine reaches late.
One more of the same shape, in the deploy's image self-check (braid-selfcheck) on the slow runner, 2026-10-18: the
solosimulated run failed on1330513after 166 s (21 s on a laptop):no event osf.session.forked, step openspec.apply.solo, from_step='openspec.propose #1'and "openspec.apply.solo does not continue openspec.propose". It passed 3 of 3 locally, and the next deploy's self-check (ead9f7e, a superset) passed it. A fork is skipped without an event only when no parent session is found foropenspec.propose #1, which fits propose needing a second attempt on a machine that slow. The scenario should name the parent step, not its first attempt, or wait for the attempt that succeeded, so one slow propose does not fail a deploy.Closing as obsolete. The three browser specs named here (
ui-polish-103.spec.ts,follow-transition.spec.ts,keyboard.spec.ts) were deleted when the suite was rebuilt (#241);ui/e2e/now has 18 journeys, which have run green on every CI run since. Thesolosimulated run from the last comment passes in./tools/sim.sh(onlye2e-lane-inferredfails, #296). If a journey fails under load again, it gets a new issue.