Loading…
Reference in a new issue
No description provided.
Delete branch "claude/test-limit-load"
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?
A fast backend test no longer fails because the machine is busy, and a test that really is slow still does. Fixes #393 and #395. Merging this deploys, so it is left for you.
What changed
docs/testing.mdandtests/support/timing.py.free_tierswas compared by identity./api/settingsparsed the built-in pipeline again. It is now parsed once, which also saves production about 30 ms per read.medium.Evidence
Backend runs clean, at this change's final settings, against the same load on today's limit.
Six tests made truly slow (a 1.5 s loop,
Event().wait(2),asyncio.sleep(2), a child onsleep 5, a child with 4 s of work, a child with 0.5 s of work then an 8 s wait) all fail on their limit, quiet and at a load of about 30, and a fast test beside them passes. The new hook test failed against today's guard before the fix. CI's run 333 on this branch passed in 44 s.What this does not settle
🤖 Generated with Claude Code
`same()` compared `free_tiers` by identity, and every read of the settings brings a new `{}`. So the refetch after a save made the form dirty again, Save turned itself back on, and the next save sent `free_tiers: {}`. The journey at operator.spec.ts:84 only passed when it saw the button before the refetch landed: 5 of 30 failed at 4 workers, and 30 of 30 pass now. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>