6dfe0c3d72
github: new check for MAVSDK tester Python scripts
5 years ago
eb1141bbea
mavsdk_tests: remove unused import
5 years ago
c6160d4e3f
mavsdk_tests: fix error for Python < 3.8
5 years ago
41341cd985
mavsdk_tests: name files consistently
5 years ago
b5048a3414
mavsdk_tests: add header and fix style
5 years ago
9b61ce1006
Tools: check style of mavsdk_tests files
5 years ago
4905ac5e2c
mavsdk_tests: add filter for cases
5 years ago
79387428c6
mavsdk_tests: fix missing space after number
5 years ago
3f1990b083
mavsdk_tests: print where to find logfiles
5 years ago
188177cef6
mavsdk_tests: print error on failure
5 years ago
ab2186f126
mavsdk_tests: improve and fix colors/result
5 years ago
b1ceef5b93
mavsdk_tests: add combined log
5 years ago
814d79cb32
mavsdk_tests: improve log file folder structure
5 years ago
8283d19682
mavsdk_tests: print overall results
5 years ago
a208129921
mavsdk_tests: satisfy mypy type checks
5 years ago
12252c97c5
mavsdk_tests: further argument cleanup, some types
5 years ago
ff64d87ae6
mavsdk_tests: import naming, easier coloring
5 years ago
11a28840f3
mavsdk_tests: split up Python script
...
Otherwise, the script will get a tangled mess.
5 years ago
b281d87b4a
mavsdk_tests: initialize Tester class in ctor
5 years ago
e2c80e546d
mavsdk_tests: properly exit on Ctrl+C
...
With threads we need to manually take care of it, otherwise it gets
messy and we need to press Ctrl+C multiple times.
5 years ago
2c2e314ffe
mavsdk_tests: improve output, allow log and stdout
...
This makes it possible to write to logfiles and at the same time print
everything to console in verbose mode.
5 years ago
d7eb600b59
mavsdk_tests: improve test name/description
5 years ago
b2e300ad1f
mavsdk_tests: improve test output readability
5 years ago
54645268ed
mavsdk_tests: only print error on failure
5 years ago
911cdc8774
mavsdk_tests: output less verbose unless needed
5 years ago
0989e90b4a
Tools: exit as straightaway with DONT_RUN set
5 years ago
bfef243dba
mavsdk_tests: write output to logs folder
...
And create folder if it doesn't exist already.
5 years ago
5ba28d417a
mavsdk_tests: try using tags as intended
...
The tags should enable use to assemble the tests in various ways. This
will probably require some iterations though.
5 years ago
512faa6ebe
mavsdk_tests: use CHECK if we don't need to abort
5 years ago
821f7c3cd9
mavsdk_tests: remove unused/not working test
...
We can add it again once fixedwing is supported. Until then, this is
just confusing.
5 years ago
fb5b05ec39
mavsdk_tests: add missing unit
5 years ago
a5d1ce91e4
mavsdk_tests: consolidate level of abstraction
...
This moves the CHECK/REQUIRE inside of AutopilotTester.
5 years ago
6a4a4bd0d6
workflows: adapt to mavsdk_tests cli changes
5 years ago
70eb444f17
mavsdk_tests: improve naming of argument
...
We abort when we already failed so this makes more sense.
5 years ago
41b2362dcf
mavsdk_tests: add more config into JSON
5 years ago
c61cd10db5
mavsdk_tests: without speedup the VTOL takes time
5 years ago
b4916fdecb
mavsdk_tests: move config into json file
5 years ago
44a556717d
mavsdk_tests: remove plane tests
...
We can put them back once it's supported.
5 years ago
ae2032d29f
mavsdk_tests: use the min of the speed factors
...
Facepalm.
5 years ago
86f24f5121
mavsdk_tests: remove opt_flow test
...
It doesn't actually seem to work.
5 years ago
b7e8837562
mavsdk_tests: add max speed factor
...
This is required because some tests don't work at more than 1x.
5 years ago
795e000c2b
simulator: remove redundant semicolon
5 years ago
d8b6c864cd
mavsdk_tests: PEP8 fixes
5 years ago
e8e8b79322
mavsdk_tests: MAVSDK is required
...
Without the library installed, we can't build and run the tests.
Silently ignoring this just leads to confusion.
5 years ago
32a6a4e8d8
Update submodule ecl to latest Wed Mar 18 12:38:43 UTC 2020
...
- ecl in PX4/Firmware (e34351229b4d9de251c495ee49e7c709a93b2521): f1aa53db8aee5e3c479bf1aa53db8a...ee5e3c479bee5e3c4f20fc08#693 )
5 years ago
b703ffa188
Update submodule mavlink v2.0 to latest Wed Mar 18 12:38:27 UTC 2020
...
- mavlink v2.0 in PX4/Firmware (d6bb5b3b9ee8bdbcfbac82bef70f12e8bdbcfbac...82bef70f12
5 years ago
640c245c44
Update submodule devices to latest Wed Mar 18 12:38:39 UTC 2020
...
- devices in PX4/Firmware (5ba8a9f62ff93843185979b3881eb7125ffc42cc): 781d4f1255c25a8f22c4781d4f1255...c25a8f22c4
5 years ago
0da7040cf5
beaglebone blue add empty px4_spi_buses
5 years ago
df5fe85cf6
github actions add linux builds
5 years ago
3233e0794d
navigator: fix edge case with valid idle setpoint
...
This is an attempt to fix an edge case in the triplet publication which
can lead to crashes on autopilots with slow SD cards.
The sequence of events before this patch is:
1. Switch to POSCTL when disarmed. At this point current valid with
setpoint idle is published.
2. Arm, takeoff, and fly using joystick/RC.
3. Switch to RTL (or trigger RTL using RC loss). At this point the
setpoint is valid but still idle and the motors will shut off.
4. Once navigator has published the new setpoint (which can take up to
1.5 seconds on slow SD cards) we will hopefully recover.
With this patch we omit this edge case, so we never publish this idle
setpoint when landed. The assumption is that this idle setpoint is no
longer required with the current flight task code, however, that needs
to be further verified.
5 years ago
Julian Oes
PX4 BuildBot
Daniel Agar