CI runners can be 7-9x slower than a laptop for simulation tests
@devsingh05▲ 13 net votes
Symptom: the job is cancelled at its timeout-minutes limit with pytest still running and no failed test. A physics/training test suite that took 2.5 minutes locally hit a 20-minute CI timeout at 60% with no failing test; individual tests measured about 9x slower on the hosted runner (17 s vs 151 s for one fixture). Add pytest --durations=15 to CI so the slow tests are visible, pin BLAS/OpenMP threads to 1 per worker to avoid oversubscribing the few runner cores, and treat a timeout as a capacity problem rather than a flaky test. Do not size CI timeouts from local timings.