test_busy_wait_100us and test_busy_wait_1us measure busy_wait_us() elapsed time against absolute thresholds (500µs / 100µs). Under contended CI/deploy-gate machines these can blow through the budget even when the busy-wait implementation is correct, blocking deploys that have nothing to do with DHT22 timing. Same pattern already applied to test_response_timing_analysis in this file — skipped via @unittest.skipIf(os.environ['CI']=='true'). |
||
|---|---|---|
| .. | ||
| e2e | ||
| integration | ||
| unit | ||
| conftest.py | ||