7c6f1cd590
Tools: build_autotest.sh: pass in --autotest-server to autotest.py
...
This will tell autotest.py to undertake the steps required for our
autotest server to run correctly
4 years ago
1c4873cece
Tools: build_autotest.sh update email address
...
drones_discuss is well obsolete. I've used ardupilot.devel@google.com for now although we could do better, or simply choose not to emit spam.
4 years ago
1104f15d88
Tools: build log message documentation on autotest server
5 years ago
49314b2b86
Tools: build_autotest.sh: install pymavlink after MAVProxy
...
Currently installing MAVProxy pulls pymavlink in as a dependency, so we
end up running whatever MAVProxy's master branch is pointing to
(currently pymavlink>=2.3.3).
ardupilot master can reference a pymavlink commit which is not part of
whatever MAVProxy's master branch is pointing to, so we end up with
failures like this in autotest:
fly.ArduCopter:
Mount (Test Camera/Antenna Mount) ('module' object has no attribute 'MAV_CMD_DO_SET_ROI_SYSID') (see /mnt/volume_nyc3_01/autotest/APM/buildlogs/ArduCopter-Mount.txt)
FixedYawCalibration (Test Fixed Yaw Calibration) ('module' object has no attribute 'MAV_CMD_FIXED_MAG_CAL_YAW') (see /mnt/volume_nyc3_01/autotest/APM/buildlogs/ArduCopter-FixedYawCalibration.txt)
If we install pymavlink after installing MAVProxy we should end up with
the pymavlink messages generated from the messages in our mavlink
subdirectory, rather that the pymavlink messages shipped as part of the
pymavlink pip release.
5 years ago
c545171cec
Tools: fixed compiler path for autotest
5 years ago
704407118b
Tools: use https:// scheme for ardupilot URLs
5 years ago
6a558bff2b
Tools: removed PYTHONPATH setting
...
this was breaking mavproxy
6 years ago
d66d1a31f0
Tools: set SITL_PANIC_EXIT for build_autotest.sh
6 years ago
2fb8aba1b2
autotest: use build path on faster filesystem
6 years ago
a745bad5b0
Tools: cleanup autotest script
6 years ago
47968cda09
scripts: don't set PKG_CONFIG_PATH globally
...
It was done only for Bebop, but we build it statically so it has
actually no effect.
8 years ago
2f8e9db606
autotest: fixed update of pymavlink
8 years ago
5d7d190394
autotest: setup PKG_CONFIG_PATH for Parrot libiio
8 years ago
c99a4a6973
Update build_autotest.sh
8 years ago
c9435963c8
autotest: use ArduPilot mavlink tree
9 years ago
27934a893e
autotest: raise timeout again
...
after trying lots of other things to speed up build_binaries.sh it
still isn't fast enough, so this just raises the timeout by 50%
9 years ago
72e4ed5665
autotest: no need to check other repos now
...
we don't need to check other repos now we use submodules for all code
9 years ago
df765f0d43
autotest: raise lock timeout
9 years ago
dea708b368
Tools: switch to ardupilot.org for firmware and autotest
9 years ago
0d9a3840d8
autotest: Added submodule update and removed old modules update
...
Firstly build.All was failing as the submodules had not been updated
so the 'git submodule update' in this commit resovles that.
Secondly, now that the dependant projects like PX4Firmware etc are git
submodules of ardupilot we no longer need to check them out separately
and update them so I have removed all those.
I left MAVProxy as it isn't a submodule of ardupilot.
9 years ago
c2a12b55a0
scripts: raise max lockage in autotest
9 years ago
b8c6bee132
autotest: raise overall timeout
9 years ago
279a320f44
Tools: switch autobuild to 4.9 compiler
9 years ago
f871f040fb
scripts: Adding AT to autotest build
10 years ago
b966f7fc3e
autotest: ensure we start on master branch
10 years ago
dd5be8837a
autotest: raise timeout
10 years ago
8d393c89d0
autotest: fixed bash syntax
10 years ago
1c94559fa2
autotest: auto-update uavcan repo
10 years ago
ce4da9b09c
autotest: raise timeout again
10 years ago
e49cd68b83
autotest: save core and elf files
...
try to catch floating pt exception causes
10 years ago
34a43b2d99
autotest: fixed backup of autotest .bin logs
10 years ago
b688577825
autotest: update compiler
10 years ago
caeb2c4d0d
autotest: raise timeout to 7000 seconds
11 years ago
0b7e96b528
autotest: ensure old tags in PX4NuttX and PX4Firmware don't get used
11 years ago
ea09aebed0
autotest: raise timelimits again
11 years ago
387b6afed4
autotest: ensure JSBSim is dead at start of testing
12 years ago
b992423f4d
autotest: log versions of trees in build log
12 years ago
935546d80d
PX4: setup build layout to assume PX4Firmware and PX4NuttX trees
...
both in directory above ardupilot
12 years ago
61507ccd20
autotest: build docs on each autotest run
12 years ago
81bb4f26a1
autotest: update plane test with more modes
...
added tests for FBWB, STABILIZE, CRUISE, ACRO and CIRCLE
12 years ago
becd180441
autotest: external timeout must be greater than internal timeout
...
or we can get blank output
12 years ago
5b29c82a2b
autotest: update timeout again
...
we're getting too close
12 years ago
757adacf8a
autotest: added $HOME/APM to PYTHONPATH
12 years ago
96df6d6f7c
scripts: allow build_parameters.sh to work from either APM directory or above
12 years ago
d7b1c69362
autotest: increase the timelimit for longer copter tests
12 years ago
7e36935140
autotest: keep images in history
12 years ago
58d5fab412
autotest: copy .tlog files to history
12 years ago
4a02af088b
autotest: check for new build tags
12 years ago
60ae67992d
autotest: fixed mavlink update path
12 years ago
94463fd91e
autotest: copy latest firmware html on each run
12 years ago
Peter Barker
auturgy
Andrew Tridgell
Lucas De Marchi
Jani Hirvinen
Grant Morphett
Andrew Tridgell