A hot laptop no longer fails the journeys, and a run says when macOS held back its cores (#396) #398
Loading…
Reference in a new issue
No description provided.
Delete branch "claude/browser-stall"
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?
Why it stalled. macOS sometimes takes the performance cores away from the scheduler, so everything shares the four efficiency cores.
kern.sched_recommended_coresdrops from 255 to 15. A 12 s browser step took 109 s and failed 4 journeys. Which journeys fail only depends on which are running, so no test is at fault. Heat is the likely reason, though macOS gives none: spinners with no browser set it off, but the same spinners later ran 345 s without it.What changes
tools/test.shends with the cores it had, when it was held back, pass or fail.docs/testing.mdhas a section, "A hot laptop".run.spec.ts:5clicked a tab under its close button, and the console missed what landed before its stream opened, so the bar's time went stale.Cost. A journey that is really broken takes 40 s per wait to fail on a laptop, not 10 s.
Verified
./tools/test.shis green: 458 backend tests and 39 journeys, in 23 s.10s, and passes 5 of 5 with the fix.Not verified. The 10 runs in a row that braid#396 asked for were not run, at the owner's word.
Closes #396
🤖 Generated with Claude Code