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> |
||
|---|---|---|
| .. | ||
| mavsdk_tests | ||
| mavros_posix_test_avoidance.test | ||
| mavros_posix_test_mission.test | ||
| mavros_posix_test_safe_landing.test | ||
| mavros_posix_tests_iris_opt_flow.test | ||
| mavros_posix_tests_missions.test | ||
| mavros_posix_tests_offboard_attctl.test | ||
| mavros_posix_tests_offboard_posctl.test | ||
| mavros_posix_tests_offboard_rpyrt_ctl.test | ||
| rostest_avoidance_run.sh | ||
| rostest_px4_run.sh | ||