You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Tests: three speed checks miss on loaded macOS and Windows runners; make them measure without testing less #890
Three tests that check a speed bound miss it on the slower macOS and Windows CI runners, though the code under test is unchanged. They show up as red advisory jobs on unrelated PRs, which hides real failures. Each should keep checking what it means to (a decision under its deadline, linear time, a fast join) in a way a loaded runner can't break, without testing less.
1.14 s (the same decide takes ~80 ms on a quiet machine, measured on #878)
A lead for the second one: both numbers are whole multiples of 1/64 s. On Windows, time.process_time ticks in 15.6 ms steps, so n measured one tick (0.015625), and the 8× ratio compares 12 ticks against 1.
Acceptance
Each test still fails on a real regression. Show it in the PR: slow the code under test on purpose (a sleep, or a quadratic loop in the linear-time case) and the test fails.
Each holds on a loaded runner. For example: measure enough work that the clock's resolution doesn't matter; compare against a baseline measured in the same test rather than a fixed number; use CPU time where the work is CPU-bound; or take the best of several runs. No bound is simply raised.
Two green runs of the macOS and Windows jobs on the PR.
Related: the Speed job's pattern budgets are #722's, so leave them out of this one.
Hi! I'd like to work on this issue as a contribution.
I plan to investigate the three timing checks, make their measurements more robust across loaded CI runners without weakening their regression detection, and add/adjust tests to demonstrate that genuine performance regressions are still caught.
I'll also verify the changes against the relevant macOS and Windows CI runs.
Thanks, @Siri-Durugapu, good to see you back after #703. I offered this one to @Seyamalam on #878 a few minutes before your comment, since they measured these misses there. If they haven't taken it by the end of 17 Nov (UTC), it's yours, and I'll assign it then.
Run Tracekit on an open-source agent built on a framework and report what broke #795: run Tracekit on an open-source agent built on a framework tracekit.instrument() wires, and report what broke. You'll need an API key for whatever model the agent uses (a local model works too, if the agent supports one).
Say which on that issue and I'll assign it.
Thanks for offering these alternatives! I'd like to take up #769 (Signer: measure the dev signer's cold start) while waiting for the availability of #890.
I'll investigate the existing signer startup flow, understand the 10-second autospawn timeout, and implement the measurement and appropriate tests.
Great, @Siri-Durugapu. GitHub only lets me assign you on an issue you've commented on, so please leave a short comment on #769 and I'll assign it there. Two at a time is fine: #769 now, and #696 once you've confirmed Pi runs for you.
Activity
Siri-Durugapu commentedon Nov 16, 2026
Hi! I'd like to work on this issue as a contribution.
I plan to investigate the three timing checks, make their measurements more robust across loaded CI runners without weakening their regression detection, and add/adjust tests to demonstrate that genuine performance regressions are still caught.
I'll also verify the changes against the relevant macOS and Windows CI runs.
Is this issue available for me to work on?
LoopGlitch26 commentedon Nov 16, 2026
Thanks, @Siri-Durugapu, good to see you back after #703. I offered this one to @Seyamalam on #878 a few minutes before your comment, since they measured these misses there. If they haven't taken it by the end of 17 Nov (UTC), it's yours, and I'll assign it then.
LoopGlitch26 commentedon Nov 16, 2026
@Siri-Durugapu, two you could start today if you'd like, either instead or while you wait:
tracekit.instrument()wires, and report what broke. You'll need an API key for whatever model the agent uses (a local model works too, if the agent supports one).Say which on that issue and I'll assign it.
Siri-Durugapu commentedon Nov 16, 2026
Thanks for offering these alternatives! I'd like to take up #769 (Signer: measure the dev signer's cold start) while waiting for the availability of #890.
I'll investigate the existing signer startup flow, understand the 10-second autospawn timeout, and implement the measurement and appropriate tests.
Please assign #769 to me. Thanks!
LoopGlitch26 commentedon Nov 16, 2026
Great, @Siri-Durugapu. GitHub only lets me assign you on an issue you've commented on, so please leave a short comment on #769 and I'll assign it there. Two at a time is fine: #769 now, and #696 once you've confirmed Pi runs for you.