It seems like we are often missing updates from topics like flight mode
or in air state, both topics that are sent out infrequenctly e.g. at 1
Hz. Therefore, instead of polling for that data we should probably
subscribe to the updates and that way get notified of each an every
update.
For instance this should prevent the case where we miss the mode change
from mission to descend and back to mission once landed and disarmed.
Depending on loop iterations for timeouts is not accurate, as usleep behavior depends on the system load and asking for a 0 ms sleep can potentially return immediately.
We had not actually properly adjusted the timeout to the lockstep speed
factor. Once we did that, we had to increase the timeouts quite a bit to
have the tests pass.
* workflows: remove unneeded pip dep and comments
* mavsdk_tests: simple test using flow/offboard
This adds a first proof of concept of a test using flow and offboard.
* Flow MAVSDK test: check against ground truth
* CleanUp
* workflows: use latest docker image with psutil
* mavsdk_tests: fix PEP8 issues
* Add VTOL CI tests back
* switch to non-rendering flow mockup
* workflows: install mavsdk from GitHub release .deb
* Add vision test and disable VTOL temporarlly
* Fist draft of combining test coverage and test in one workflow
* Add VTOL mavsdk tests back in CI
Co-authored-by: Julian Oes <julian@oes.ch>
Co-authored-by: kritz <kritz@ethz.ch>
