-
Notifications
You must be signed in to change notification settings - Fork 13.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] CI on main fails #23200
Comments
This issue has been mentioned on Discussion Forum for PX4, Pixhawk, QGroundControl, MAVSDK, MAVLink. There might be relevant details there: |
Thanks @MaEtUgR. I wonder if I should have been able to catch this before hitting the release. |
@julianoes have been... let's fix things and take learnings 👍 Thanks for all your efforts. I think it's now down to flash overflow issues and possibly some (intermittent?) Jenkins problem. I'll keep this issue updated. |
Since #23088 FMU-V5 Stackcheck is overflowing |
@PetervdPerk-NXP Sad story but it looks to me like #23169 freed up some flash again. Thanks to everyone involved! |
Describe the bug
fixed by CameraFeedback: shorten line length such that documentation parser works #23192
fixed by Jankinsfile-compile: add missing comma after
ark_pi6x_default
#23198fixed by board hkust_nxt-dual fix hw_config.h missing APP_RESERVATION_SIZE, which causes CI bug #23204 instead of hjust_nxt-dual board_config: disable FLASH_BASED_PARAMS to fix CI #23197
fixed by nxp/imxrt_common/main:Fix Breakage from a9962dc #23174
Flash overflow.
Both heavy flash overflow. Any idea? @dagar ? 😇
@sfuhrer started looking into it @haumarco continued. Minimal fix: mavsdk_tests: increase acceptance radius for position check on offboard landing #23190
@PerFrivik started looking into it: Increase threshold for yaw_error_std #23196
To Reproduce
Look at CI report on new commits on main.
Expected behavior
Passing CI such that PRs see when they brake things.
Screenshot / Media
No response
Flight Log
See screenshots
Software Version
main branch
Flight controller
CI
Vehicle type
None
How are the different components wired up (including port information)
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: