The ESP32-S3 reset integration is blocked in a clean checkout because python/fbuild/_native.pyd is stale relative to crates/fbuild-python/src/lib.rs.
Repro on the attached COM13 board:
cargo build -p fbuild-python
python -m pytest tests/test_serial_reset.py -q
- The import resolves to
python/fbuild/_native.pyd, which in this checkout does not expose SerialMonitor.reset_device.
- If I stage the fresh
target/debug/_native.dll into a temp package and rerun, the method exists and the HTTP reset returns success.
Observed behavior:
- Plain
python -m pytest tests/test_serial_reset.py -q fails with ModuleNotFoundError or AttributeError depending on the import path.
- The repo docs imply the Python package should re-export the Rust
_native extension, but the checked-in binary is out of sync with the source.
This blocks physical-board validation unless the package is rebuilt/installed first.
The ESP32-S3 reset integration is blocked in a clean checkout because
python/fbuild/_native.pydis stale relative tocrates/fbuild-python/src/lib.rs.Repro on the attached COM13 board:
cargo build -p fbuild-pythonpython -m pytest tests/test_serial_reset.py -qpython/fbuild/_native.pyd, which in this checkout does not exposeSerialMonitor.reset_device.target/debug/_native.dllinto a temp package and rerun, the method exists and the HTTP reset returns success.Observed behavior:
python -m pytest tests/test_serial_reset.py -qfails withModuleNotFoundErrororAttributeErrordepending on the import path._nativeextension, but the checked-in binary is out of sync with the source.This blocks physical-board validation unless the package is rebuilt/installed first.