forked from Archive/PX4-Autopilot
9c001f2e40
* MAVSDK_Test_Runner: Place PX4 instance runner after Gazebo server runner - This was a nasty bug where starting PX4 instance first, then starting Gazebo server was causing PX4 instance' EKF to freak out, probably because it doesn't like getting data a while after it is started - Detailed breakdown is given here: https://github.com/PX4/PX4-Autopilot/issues/21229#issuecomment-1450761542 - This now guarantees that such edge case won't occur and MAVSDK test will run as it should * MAVSDK Test Runner: Retain comment within 79 character limit - To pass flake8 python style check * Update test/mavsdk_tests/mavsdk_test_runner.py Co-authored-by: Julian Oes <julian@oes.ch> --------- Co-authored-by: Julian Oes <julian@oes.ch> |
||
---|---|---|
.. | ||
catch2 | ||
configs | ||
.gitignore | ||
CMakeLists.txt | ||
MAVSDK_VERSION | ||
autopilot_tester.cpp | ||
autopilot_tester.h | ||
autopilot_tester_failure.cpp | ||
autopilot_tester_failure.h | ||
autopilot_tester_follow_me.cpp | ||
autopilot_tester_follow_me.h | ||
logger_helper.py | ||
math_helpers.h | ||
mavsdk_test_runner.py | ||
process_helper.py | ||
test_main.cpp | ||
test_multicopter_control_allocation.cpp | ||
test_multicopter_failsafe.cpp | ||
test_multicopter_failure_injection.cpp | ||
test_multicopter_follow_me.cpp | ||
test_multicopter_manual.cpp | ||
test_multicopter_mission.cpp | ||
test_multicopter_offboard.cpp | ||
test_vtol_mission.cpp | ||
vtol_mission.plan |