The ESP32 BMP280 example compile was timing out at 98% (1473/1483 build steps), failing with the unhelpful "ESP-IDF build timed out (300s)" message even though every individual step was healthy. Cold ESP-IDF builds that pull in external Arduino libraries — Adafruit BMP280 + Adafruit BusIO + Adafruit Unified Sensor on top of the base arduino-esp32 component tree — routinely produce ~1480 build objects. On modest VPS hardware this takes 5-7 minutes the first time. Ninja's incremental cache makes subsequent compiles seconds, but the first one needs more headroom. Constant lifted to NINJA_TIMEOUT_S so the value used in the timeout matches the value reported in the error message — the previous code hard-coded "300s" in two places that were free to drift apart. Repro before: open the example "ESP32 — BMP280 Barometric Pressure" on velxio.dev/editor on a clean container, click compile → fails after 5 minutes with timeout. After: completes in ~6 minutes on the first run, ~5 seconds on subsequent runs. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| esp-idf-template | ||
| picow_net | ||
| __init__.py | ||
| arduino_cli.py | ||
| chip_compile.py | ||
| esp32_flash_image.py | ||
| esp32_i2c_slaves.py | ||
| esp32_lib_bridge.py | ||
| esp32_lib_manager.py | ||
| esp32_spi_slaves.py | ||
| esp32_worker.py | ||
| esp_qemu_manager.py | ||
| espidf_compiler.py | ||
| gpio_shim.py | ||
| metrics.py | ||
| picow_net_bridge.py | ||
| project_files.py | ||
| qemu_manager.py | ||
| wasm_chip_runtime.py | ||
| wasm_chip_slave.py | ||
| wifi_status_parser.py | ||