0761aeff5a
Tools: split yaw-vehicle-for-mount-roi test out
2021-07-25 09:30:25 +10:00
9205f379cf
autotest: increase number of parameter retries
...
sets were failing just after we uploaded very large numbers of
parameters. I'm guessing the parameter queue in ArduPilot is still
full.
2021-07-04 08:19:11 +10:00
1e55b377c1
autotest: shift where we print which attempt we are doing
2021-07-04 08:19:11 +10:00
55e8922c3c
autotest: correct placement of not-alive-after-test message
...
This was misplaced with bad conflict resolution
2021-07-04 08:19:10 +10:00
e51631c8b0
autotest: emit 'attempt 1/3' when retrying set_parameter
...
Also reterm things in terms of attempts rather than retries
2021-07-04 08:19:10 +10:00
19e3e3d1a0
autotest: ensure no stray message listeners after test
2021-07-04 08:19:10 +10:00
824a50999e
autotest: timeout in wallclock time in config error loop test
...
SYSTEM_TIME is not sent in config error loop
2021-07-04 08:19:10 +10:00
ec1cf2f3af
autotest: let arming failure messages get spit out
2021-07-04 08:19:10 +10:00
cea0d7c971
autotest: move autotest tlog files into buildlogs directory
2021-06-11 22:14:11 +10:00
14b2af84ab
autotest: break out a home_relative_loc_ne for getting a home-rel loc
2021-06-11 16:59:51 +10:00
96e14d470a
autotest: retry SITL connect many times while running under GDB
...
Allows for easier debugging under gdb when checking startup code
2021-06-11 11:15:58 +10:00
0b517cfc57
autotest: start GDB in tui mode by default
2021-06-10 20:52:48 +10:00
79de738266
autotest: wait for a few seconds for arm-failure messages to appear
...
If prearms never come true then we try to arm the vehicle so it tells us
what is wrong. Since we no longer push statustexts hard, we have to
wait for the reasons to come out at normal clocked rates.
2021-06-09 14:13:54 +10:00
6af6d2fc2a
autotest: add a progress message for looking for a message in a log
2021-06-09 14:13:31 +10:00
6944ef6af1
autotest: fly each working Helicopter frame
2021-06-09 12:15:42 +10:00
b14dcf1df5
Tools:autotest: updated FRSky SPort test to use new 2 byte data IDs
2021-06-02 17:33:15 +10:00
8925c2830b
autotest: check fence upload/download when creating from locs
2021-06-01 15:54:59 +10:00
3eb164fb6a
autotest: move script helper functions from rover to common
2021-05-14 13:21:36 +10:00
3d562046da
autotest: add accuracy option to guided_achieve_heading
2021-05-14 13:21:36 +10:00
9965f1a31d
autotest: add some helpers for local-position movement
2021-05-12 13:01:50 +10:00
765889b827
autotest: don't send statustext during exception
...
During an exception we don't want to be trying to print these
2021-05-07 14:21:44 +10:00
f78cf73726
autotest: don't fail completely if ArduPilot process dies
2021-05-07 12:22:11 +10:00
9a13b5c9b6
autotest: add test for auxfunc triggering via script
2021-05-05 07:13:18 +10:00
8fdfdebe55
autotest: pass sitl_commandline_customised up the context stack
...
We're running tests on the Callisto frame when we shouldn't in Copter as
the information was lost in nested Contexts.
We can only reset the SITL commandline at an actual Test level - if a
defaults file has been used then it is unclear as to what the state of
any parameter is in storage as we move between contexts
2021-05-01 17:22:36 +10:00
c7c4c17c68
autotest: improve change_mode debug
2021-05-01 13:25:13 +10:00
fc426e01c2
autotest: stop using start_test for things that aren't actually tests
...
start_test should only be used for top-level tests, not parts of
top-level tests
2021-04-28 13:53:46 +10:00
30e8160aa1
autotest: sort logs before moving
...
Makes it easier to find last log in output.
Also removing pointless lamdaing of some functions
2021-04-21 13:16:24 +10:00
0ee0228883
autotest: fix flapping fly-home-land-and-disarm
...
One of the tests just happened to be within acceptance radius of
waypoint 8 - so when we set that as a waypoint we never saw it actually
be our waypoint so the set_waypoint failed
2021-04-20 23:04:24 +10:00
8643322f06
autotest: correct string we expect from MAVProxy
...
Was APM: now AP:
2021-04-20 14:08:12 +10:00
c12d1938c2
autotest: add a test for button change for changing modes
2021-04-19 14:27:45 +10:00
dfa342a79f
autotest: correct rc-values-good debug
2021-04-03 08:59:14 +11:00
d2c00f7b26
autotest: ensure RC thread is killed after each run_test
...
Every run_test starts a thread. del is not being called. So clean it
up in the caller
2021-04-01 11:00:54 +11:00
ba972b6b46
autotest: fix --map option
2021-03-31 16:30:25 +11:00
e8f96efe72
autotest: wait for stats initialisation before rebooting
...
If the RTC time we reset parameters (STAT_RESET) is zero then we reset all parameters.
In SITL we only set that time if we see a GPS due to the AP_RTC RTC_TYPES parameter default bitmask value of 1
So if you reboot SITL fast enough while STAT_RESET is zero you can see that STAT_BOOTCNT does not increase. Easily reproducible in SITL; start with -w and type reboot in several times before SITL sees the GPS come up and you can see STAT_BOOTCNT doesn't increase.
Fix is to ensure STAT_RESET is non-zero before rebooting.
2021-03-31 13:33:39 +11:00
240e2d6b28
autotest: correct pexpect handling of supplementary programs
2021-03-24 23:10:27 +11:00
ae7b21843e
autotest: remove useless mavproxy set heartbeat directive
...
This has never actually worked:
2021-03-24T04:53:03.7594996Z AT-0040.3: Starting MAVProxy
2021-03-24T04:53:03.7595674Z PYTHONPATH: /__w/ardupilot/ardupilot/Tools/mavproxy_modules
2021-03-24T04:53:05.8106006Z Running: "mavproxy.py" "--master" "tcp:127.0.0.1:5762" "--aircraft" "test.ArduCopter" "--sitl=127.0.0.1:5502" "--streamrate=5" "--cmd="set heartbeat 8"" "--target-system=1" "--target-component=1" "--quadcopter" "--default-modules" "misc,terrain,wp,rally,fence,param,arm,mode,rc,cmdlong,output"
2021-03-24T04:53:05.8108569Z ERROR LOADING MAVNATIVE - falling back to python implementation
2021-03-24T04:53:05.8109340Z Connect tcp:127.0.0.1:5762 source_system=255
2021-03-24T04:53:05.8109962Z no script test.ArduCopter/mavinit.scr
2021-03-24T04:53:05.8110739Z Unknown command '"set heartbeat 8"'
2021-03-24 23:10:06 +11:00
8bf1ac0347
autotest: fix and tidy the log download test
...
We were requesting past the end of the file
2021-03-24 14:46:48 +11:00
fdbbcaa506
autotest: bump default speedups for several vehicles
...
These tests seem to run stabley on my box with essentially no speedup
limit
2021-03-24 14:46:48 +11:00
6f2de67ead
autotest: augment delay_sim_time debug
2021-03-24 14:46:48 +11:00
d9501766c7
autotest: augment delay_sim_time debug
2021-03-24 08:57:03 +11:00
073a9e3390
autotest: fix frsky passthrough test
...
Mainly through polling much faster, but also allowing for statustexts in
different orders from frsky/statustext
2021-03-22 18:08:44 +11:00
e567cca230
autotest: drain mav before receiving system_time in get_sim_time
2021-03-19 09:46:45 +11:00
8901efd69d
autotest: start and stop MAVProxy for alttype and surface tracking tests
...
autotest doesn't currently supply terrain tiles, so MAVProxy must be
started
2021-03-19 09:46:45 +11:00
19e5351631
autotest: start and stop mavproxy for setpoint tests
...
These work in terrain frame - but autotest won't satisfy terrain
requests yet
2021-03-19 09:46:45 +11:00
462ac255a3
autotest: start MAVProxy only as needed for testing
2021-03-19 09:46:45 +11:00
4269cf52a2
autotest: split application of default parameters and defaultfile parameters
...
ensures all vehicles have LOG_DISARMED
2021-03-19 09:46:45 +11:00
dbee2e5d71
autotest: ignore type=0 heartbeat packets on SITL start
...
Until ArduCopter allocates its motors backend we emit a generic type,
for which there is no mode map in pymavlink.
So don't consider the reboot complete until we see a valid heartbeat.
2021-03-19 09:46:45 +11:00
ec15614e11
Tools:autotest: added frsky passthrough autotest for terrain message frame 0x500B
2021-03-18 21:43:48 +11:00
21c124ab47
autotest: tidy set_parameters
...
Remove commented code, add more to the verbose option
2021-03-18 11:29:45 +11:00
da52e5d08c
autotest: set SYSID_MYGCS in tests which need it
...
This was still relying on heartbeats coming from MAVProxy. As speedup
increased those heartbeats may not come fast enough - and they really
should be coming from autotest as that's who's doing the commanding.
autotest: set SYSID_MYGCS in AFS test
autotest: set SYSID_MYGCS before setGCSfailsafe
2021-03-17 16:02:45 +11:00
Peter Barker
yaapu