Repository navigation
test(ceremony): show why the Worker-transition e2e failed - #98
Merged
Merged
Conversation
Firefox once failed this run in CI about three seconds into Prefetch, before OAuth. 38 local repetitions, including the full Firefox suite on two CPUs, did not reproduce it, and the trace held only status: failed. The e2e app now keeps the failure's display text, and the test asserts on it together with the result, so the next failure names its cause. Signed-off-by: Wondertan <hlibwondertan@gmail.com> Assisted-by: Claude Opus 5.5
This was referenced Oct 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Once in CI, Firefox failed the old-to-new Worker transition e2e (from #80): Prefetch reported
failedabout three seconds in, before OAuth (run 37027608511 on #97). It hasn't reproduced locally in 38 runs, including the test alone, the full asset suite and the whole Firefox job set pinned to two CPUs. The uploaded trace only saysstatus: failed.The e2e app now keeps the failure's display text, and the test asserts on it together with the result. The next CI failure will then name its cause: a missing pinned Worker, a redundant Worker, a refused dispatch, or a connection failure. Test-only; no product change.