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'). |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| test_arduino_cli_attinycore.py | ||
| test_boot_images.py | ||
| test_compile_dedup.py | ||
| test_dht22_worker.py | ||
| test_esp32_wifi_args.py | ||
| test_esp32_wifi_webserver.py | ||
| test_esp32c3_wifi_args.py | ||
| test_espidf_compiler.py | ||
| test_espidf_real_paths.py | ||
| test_i2c_slaves.py | ||
| test_mcp_tools.py | ||
| test_signal_router.py | ||
| test_wifi_status_parser.py | ||