bbc2b703c3
mavsdk_tests: update catch2 to 2.13.8
...
Fixes this issue on Fedora: https://github.com/catchorg/Catch2/issues/2178
3 years ago
07d75d85cf
mavsdk_tests: trigger flush to stdout every second
3 years ago
2d8ebc6839
mavsdk_tests: add timestamp to log output
...
The timestamp is added when the output is queued up, rather than later
when the queue is emptied and some time might have passed.
3 years ago
dd6fb58f82
mavsdk_tests: don't stall mavsdk_tests binary
...
This is an attempt to fix the test failure where PX4 detects an RC
timeout presumably because the tester process mavsdk_tests is stalled
and does not send RC control messages in time.
3 years ago
199b5e7d48
Revert "mavsdk_tests: retry gz model spawn command"
...
This reverts commit c15d3f7cfa
3 years ago
9184038359
mavsdk_tests: try to restart gzserver
...
Sometimes gzserver seems to just not start correctly. With this commit
we try to just restart.
3 years ago
9894598b63
mavsdk_tests: update to be able to fetch rtps builds as well
3 years ago
9312c772f1
mavsdk-tests: Re-try to launch a mission for some time before failing. This mitigates an issue where the flight controller has an uploaded mission, but has not finished the mission feasibility checks yet.
3 years ago
764af19da4
mavsdk_tests: bump MAVSDK version to v0.48.0
...
This might help with CI tests where we get RC loss because, presumably,
MAVSDK is not sending them in time.
3 years ago
dcf69144cb
mavsdk_tests: fix type for mypy check
...
This was probably triggered due to a mypy update.
3 years ago
94884594bb
mavsdk_tests: check gzserver and gz model calls
...
This adds two checks to make sure gzserver has actually started before
continuing, and also whether the gz model call was successful.
3 years ago
c15d3f7cfa
mavsdk_tests: retry gz model spawn command
...
This should help when gzserver does not respond yet and we end up
without a model and hence can't connect later and time out.
This change also required a fix to prevent the tester to hang on
terminating all runners. By using poll instead of only read we can
prevent that and actually properly join the logger thread.
3 years ago
06a91ec752
Improve offboard failsafe ( #18160 )
...
* state_machine_helper: improve offboard failsafe
* state_machine_helper: add missing parameter to set_link_loss_nav_state
* state_machine_helper: fix no rc and offboard reason
* Fix offboard test by enabling rcl_except
* mavros_test fix offboard_posctl_test with rcl_except
* autopilot_tester make RcLossException bits explicit
Co-authored-by: Julian Oes <julian@oes.ch>
* autopilot_tester change rcl_except to rc_loss_exception
Co-authored-by: Julian Oes <julian@oes.ch>
* autopilot_tester fix rc_loss_exception renaming errors
Co-authored-by: Julian Oes <julian@oes.ch>
3 years ago
44f12acafe
mavsdk tests: remove hover missions for VTOL
...
Signed-off-by: Silvan Fuhrer <silvan@auterion.com>
4 years ago
af50e25647
mavsdk_tests: update to MAVSDK v0.41.0
...
This required replacing some of the methods which had been deprecated
and now removed.
4 years ago
c4d54d983b
mavsdk_tests: bump MAVSDK version to 0.40.0
4 years ago
4f52c0b6da
mavsdk_tests: unused var and index fix
4 years ago
f16913c175
mavsdk_tests: fix timeout at 1x speed
4 years ago
e7fcfbf658
mavsdk_tests: use global position instead of local
...
We are currently not testing with flow only anyway, so we might as well
remove this for now.
4 years ago
43fccece61
mavsdk_tests: check installed version
...
Starting with MAVSDK 0.39.0 we can specify the version required. This
way we can fail at configure time instead of later during compilation or
linking.
4 years ago
7384bd2675
mavsdk_tests: specify required MAVSDK version
...
This way it can be better picked up by CI scripts.
4 years ago
bb0fe9ee61
mavsdk_tests: losen time limit for VTOL mission
4 years ago
2eaf677de3
mavsdk_tests: correctly locate plan
4 years ago
cd66a79747
mavsdk_tests: move waypoints to vehicle position
...
This way it shouldn't matter where the test is run.
4 years ago
d714c2faec
mavsdk_tests: add VTOL mission tests
...
This adds VTOL mission tests to the CI integration tests.
This depends on MAVSDK v0.38.0.
4 years ago
1e88939605
mavsdk_tests: report speed factor every second
...
This helps in debugging slow CI.
4 years ago
82200fab9e
mavsdk_tests: relax MC "Fly straight" speed threshold
4 years ago
46e75ebddb
mavsdk_tests: remove leftover debug line
4 years ago
2703a34900
mavsdk_tests: add link back to github action
4 years ago
64d0ce43b6
mavsdk_tests: upload to logs.px4.io in test_runner
...
By doing the upload directly inside the mavsdk_test_runner.py we have
more context such as the model, case, etc.
4 years ago
2315618b85
mavsdk_tests: use autopilot timestamps to sleep
...
This way we should be able to avoid some of the timeouts happening on
the PX4 side if MAVSDK doesn't send setpoints in time.
4 years ago
6c26387e85
mavsdk_tests: try to prevent auto-disarm
...
We should not spend too much time sending RC init messages because if it
takes too long, we might auto-disarm in the meantime.
4 years ago
c1de27acf7
mavsdk_tests: use more conservative speed_factor
4 years ago
0ebb8c6981
mavsdk_tests: use microseconds to avoid sleep(0)
4 years ago
b6b9ce5f11
mavsdk_tests: robustify test by climbing longer
4 years ago
b79553862e
mavsdk_tests: remove timeout for mission upload
...
Just use what is MAVSDK internal.
4 years ago
aca1e85da4
mavsdk_tests: don't forget to check for rootfs dir
4 years ago
4184c204c4
autopilot_tester: don't poll mission progress
...
Instead use subscription here as well in order not to miss an update.
4 years ago
2971ce8664
mavsdk_tests: don't clear logs
4 years ago
176d932f23
mavsdk_tests: prevent missing updates
...
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.
4 years ago
2772022785
mavsdk_tests: disable mag stuck test
...
The estimator sometimes diverges in vz after landing which makes the
test fail. This needs to be dealt with first before we can enable the
test again.
4 years ago
e592bed7d3
mavsdk_tests: use timestamp from attitude field
...
The flight_information field was not updated often enough which lead
to timeouts.
4 years ago
397fa84cd0
mavsdk_tests: add time in front of debug lines
4 years ago
14cb98a6b4
Increase corridor check thresholds for mission tests
4 years ago
fda63f802e
Tone alarm: Adjust log levels
...
The earlier log levels represented normal operation scenarios as errors, this aligns the log levels.
4 years ago
3cc53f551d
MAVSDK tests: Use full system timeout off
...
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.
4 years ago
565da15f2f
MAVSDK test: Increase timeout
4 years ago
fb1f360724
mavsdk_tests: consistent 180s disarm timeout
4 years ago
f5660c6b0c
mavsdk_tests: adjust px4 and gzserver priority relative to mavsdk_test
...
- this is to avoid starving the test runner
4 years ago
a8f665739d
mavsdk_tests: manual fly forward for slightly longer
4 years ago
Beat Küng
Julian Oes
TSC21
Thomas Debrunner
benjinne
Silvan Fuhrer
Daniel Agar
Julian Kent
Lorenz Meier