Comparing 3bc6680982..fa537f9e73 - tractor - Pikers Dev

..

Author	SHA1	Message	Date
Gud Boi	fa537f9e73	Use `cpu_perf_headroom()` for timing-test deadlines `cpu_perf_headroom()` is a strict SUPERSET of `cpu_scaling_factor()` — it folds in static cpu-freq scaling + the slow-CI bump AND the sustained-load power-cap throttle probe. Point the timing-deadline call sites at it so they're robust to sustained throttling too (the gremlin behind mass `trio` deadline-miss flakes), - `test_legacy_one_way_streaming`: `time_quad_ex` cancel-deadline + `test_a_quadruple_example`'s `this_fast` smoke bound. - `test_cancellation`: `test_cancel_via_SIGINT_other_task` + `test_fast_graceful_cancel_*` deadlines. `cpu_perf_headroom >= cpu_scaling_factor` always, so never less headroom (CI stays green); `cpu_scaling_factor()` remains the internal static component. (this patch was generated in some part by [`claude-code`][claude-code-gh]) [claude-code-gh]: https://github.com/anthropics/claude-code	2026-06-25 12:53:22 -04:00
Gud Boi	fe5e1404c6	Add `cpu-perf-check` sustained-throttle gate script Standalone CLI companion to `cpu_perf_headroom()` (`20cb99ec`): idle freq snapshots LIE — every static knob (`governor`, EPP, `platform_profile`, `scaling_max_freq`) can read "performance" while a firmware/EC power cap (AMD PPT/STAPM + friends) clamps the package to ~30% the moment a sustained multi-core load lands, masquerading as a `trio`-backend deadline-miss "regression" on byte-identical code. Deats, - burns every core for `CPU_PERF_SECS` (default 4s) and samples the ACHIEVED `scaling_cur_freq` steady-state (post boost-ramp) vs the package max ceiling, - exits 0 when the sustained fraction clears `CPU_PERF_HEALTHY_FRAC` (default 0.45), 1 when throttled — so it gates a suite run: `scripts/cpu-perf-check && pytest tests/ ...`, - prints the static knobs first (to show they all read fine) then the remediation list on failure (`platform_profile` bounce, USB-C PD replug, `ryzenadj`, reboot) w/ the key reminder: do NOT bump test budgets — the box is slow, not the code. (this patch was generated in some part by [`claude-code`][claude-code-gh]) [claude-code-gh]: https://github.com/anthropics/claude-code	2026-06-25 12:53:22 -04:00
Gud Boi	e8830ac7ce	Add `cpu_perf_headroom()` for throttle-aware deadlines Mass `trio` deadline-miss failures on byte-identical code turned out to be a firmware/EC power-cap (AMD PPT/STAPM) clamping the all-core sustained clock while every static knob (`governor`, `scaling_max_freq`, EPP, platform-profile) still read "performance" — invisible to the existing `cpu_scaling_factor()` check. See `scripts/cpu-perf-check` + the `ai/conc-anal/trio_033_cancel_cascade_slowdown_depth3_issue.md` notes. Deats, - add `_measure_sustained_headroom()` to `tests/conftest.py`: a one-shot ~0.9s all-core burn (explicit `fork`-ctx `mp` procs) sampling achieved-vs-max freq AFTER the boost window; under a 0.6 gate it returns the full inverse fraction (capped 4x), else 1.0; best-effort 1.0 on non-linux or any error, - add `cpu_perf_headroom()`: `max()` of the static scaling factor and the (session-cached) sustained probe, - inflate deadline budgets by it in `test_dynamic_pub_sub`, both `test_clustering` cases, the `test_multi_nested_subactors_error_through_nurseries` pexpect waits + `test_nested_multierrors`, - `xfail(strict=False)` `test_nested_multierrors` depth=3 under throttle: the deep tree trips tractor's INTERNAL reap deadlines (`soft_kill`/`hard_kill` `terminate_after=1.6`) minting a `Cancelled` inside the runtime — not fixable by test-budget inflation; auto-clears once the box un-throttles. (this patch was generated in some part by [`claude-code`][claude-code-gh]) [claude-code-gh]: https://github.com/anthropics/claude-code	2026-06-25 12:53:22 -04:00
Bd	d95cd94e20	Merge pull request #465 from goodboy/trio_033_upgrade Add `supervise_run_process()` to `trionics`	2026-06-24 23:30:18 -04:00

Diff Content Not Available