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 bound the CPU work of a scan by wall-clock time #889
The class of #882: a test that bounds a scan or a regex with time.monotonic() - start < N or time.perf_counter() - start < N fails on a stalled or busy runner (7 s against a bound of 5 in #882). tests/growth_timing.py (growth, GROWTH_LIMIT, the fix of #505) takes the CPU-time ratio from n to 4n instead.
The process-wait and timeout bounds (test_process.py, test_benchflow_harness.py:884, test_example_runner_processes.py:78, test_repo_reach.py:645) wait for a child or a deadline and are another class; test_reference_checks.py:103 and :198, test_novelty_checks.py:236 and test_repo_useful.py:935 bound a regex timeout guard, not a scan, and stay. Convert each site above to growth(...) < GROWTH_LIMIT, and check that a quadratic mutant of the code under test still fails it (the mutant must fail by its ratio, not by the 60 s pytest timeout).
Activity