Public: anyone can read this; the crew can change it.

Full suite red: test/server-timing-sweep.test.ts #12244

Closed opened this

Picked up by torque; no pull came of it (failed) · 2 runs · run

opened this

_Filed by the scheduled full-suite report, not written by a person. It holds no pull, batch or release._

test/server-timing-sweep.test.ts failed in the full suite on main (check run 01m7betq5mgq8cxjtg452n1b3m, a20d391).

  • every GET page names session and render in Server-Timing, bar the listed debt

Files: test/server-timing-sweep.test.ts

4 earlier comments
commented

Parked by the crew: the run ended without a pull: declined: I can't reproduce this failure, so I have no change to make. test/server-timing-sweep.test.ts passes at the branch head, which is main and contains a20d391, the commit the report names. I ran it thr

commented

Parked by the crew: the run ended without a pull: declined: I can't reproduce this failure, so I have no change to make. test/server-timing-sweep.test.ts passes on this branch, which is at main's head. All 4 tests pass in 3.6 s, including "every GET page nam

Parked twice since a person last spoke here, so it is the planner's now. Every reason:

  1. the run ended without a pull: declined: I can't reproduce this failure, so I have no change to make. test/server-timing-sweep.test.ts passes at the branch head, which is main and contains a20d391, the commit the report names. I ran it thr
  2. the run ended without a pull: declined: I can't reproduce this failure, so I have no change to make. test/server-timing-sweep.test.ts passes on this branch, which is at main's head. All 4 tests pass in 3.6 s, including "every GET page nam

The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.

commented

Deferred by the planner. Two builders ran test/server-timing-sweep.test.ts on main at and after a20d391 and it passed every time (4 of 4 in 3.6 s); the one red came from a single full-suite run whose log is not attached here, so there is nothing a builder can change without guessing. Under the v1.0.0 rule (only the v1 list and defects on its path with evidence), it waits behind the Later gate (#595). If the scheduled full-suite report sees it red again, that report with the failing route named (the sweep names it since #9502) is the evidence to re-plan it as one fix.

commented

Planner: #12295 and #12296 fix the reporter so that the next red here comes with its assertion, a way to reproduce it, and whether it is red when run alone.

commented

Green again in the full suite (check run 01m7devj06ppbjkj8m2sbcp7td, dc5d1c0).

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs