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'). |
||
|---|---|---|
| .. | ||
| autosearch | ||
| backend | ||
| esp32 | ||
| esp32-emulator | ||
| esp32_cam | ||
| multi_board | ||
| multi_board_esp32 | ||
| pi_arduino_serial | ||
| pico_doom_demo | ||
| test-esp32-cam | ||
| test-esp32-p4 | ||
| test_100_days | ||
| test_Raspberry_Pi_Pico_W | ||
| test_chip_backend_runtime | ||
| test_circuit | ||
| test_custom_chips | ||
| test_custom_chips_boards | ||
| test_epaper | ||
| test_intel | ||
| docker-errors-2026-04-19.md | ||