fix(autoresearch): resolve fbuild release firmware - #4029
Merged
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthrough
ChangesFirmware path resolution
Estimated code review effort: 2 (Simple) | ~10 minutes ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
zackees
marked this pull request as ready for review
August 25, 2026 06:29
This was referenced Aug 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
.fbuild/build/release/firmware.binlayout.fbuild/build/<env>/release/firmware.binlayoutValidation
uv run pytest ci/tests/test_fbuild_default_selection.py ci/tests/test_ota_peer_hardening.py ci/tests/test_autoresearch_phases.py -q— 205 passedbash lint ci/autoresearch/build_driver.py ci/tests/test_fbuild_default_selection.py— passed/clud-review— cleanfbuild port scan— RP2350W COM18 and ESP32-C6 COM9 healthybash autoresearch rp2350w --net-peer --ota --upload-port COM18 --peer-environment esp32c6 --peer-upload-port COM9 --timeout 120s --skip-lint— cleared the previous missing-firmware failure, accepted the artifact, and reached OTA RPC executionRemaining HIL result
The peer run now proceeds through
beginOtaArtifact, then the ESP32-C6 times out on response ID 3 at the firstwriteOtaArtifactchunk. That later transport/storage failure is separate from this path-resolution fix.Relates #3956
Summary by CodeRabbit
Bug Fixes
Tests