CI: convert missions to QGC plan format #8982
Merged
Conversation
This file contains 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
if the vehicle doesn't land and disarm at the end of the mission, the current sequence doesn't reset to 0
|
I added the mission descriptions here: #8915 Also, If we can now assume that all missions will have a |
|
Yes let's assume it's .plan only from this point on. |
lamping7
force-pushed
the
pr-ci_mission_tests
branch
from
82dfbc0
to
399ab0d
Compare
dagar
approved these changes
Mar 1, 2018
|
Thanks, this is much better. |
|
Thanks, this is much better. |
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.
@dagar Do we want to modify/remove vtol_old_3? It was failing CI because the mission doesn't include landing, preventing the current sequence from resetting to 0. I've fixed how the end of the mission is detected, but now, because there is not another mission item, the vehicle begins to steer away from the WP, to loiter around it, causing a "yaw error mean" failure in the post mission check. What makes this mission different from the others is that it uses MAV_CMD_NAV_WAYPOINT to takeoff and goto the first WP.