bb0920d56a
Tools: build_parameters: remove unused function parameters
5 years ago
e15bb744ff
Tools: improve build_bootloaders.py script
...
give list of failed builds
5 years ago
0f7de04d79
Tools: added image_size to manifest
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
d464db9c70
Tools: create log of build_binaries.py builds
5 years ago
194998d631
travis: restore fly.ArduCopter as running all tests
5 years ago
82f53abee2
autotest: restore fly.ArduCopter as running all tests
...
the test list for ArduCopter is made up of those from tests1 and tests2
5 years ago
05a0fe615b
Tools: split Copter tests into two runs to balance time on travis
5 years ago
1d8a9ab556
Tools: make dumpstack and run-coverage .sh script
5 years ago
097cffaa06
Tools: build_ci: remove useless check for waf support
5 years ago
14e758a6d1
Tools: add sitltest-tracker into build_ci.sh
5 years ago
01b5337d91
Tools: auto-build f303-M10025
5 years ago
b854fa3d4e
Tools: added CUAV-Nora to autobuild
5 years ago
93ac71095d
Tools: build_binaries, sort boards before building, print board counts
5 years ago
b3ff75ed6b
Tools: fixed list for USBID in generate_manifest.py
5 years ago
d87306afbd
Tools: auto-build f303-Universal firmware
5 years ago
0d283bf3a7
Tools: added --build-target to configure_all.py
5 years ago
a777031f54
Tools: auto-build R9Pilot
5 years ago
e2ac1acfcc
Tools: added SuccexF4 to auto build
5 years ago
2342ea600a
Tools: exclude build-linux-libraries and gtest from coverage analysis
...
The build-linux-libraries were mavlink-generated headers created when we
build the examples. We don't intentionally try to test anything in
there at the moment, so it's noise.
5 years ago
82148607ee
Tools: add USBID to generated apj file
5 years ago
57300d0769
Tools: remove build before running coverage
...
Stop losing a run because a file has been removed.
5 years ago
26e0f5c084
Tools: add python version option to configure_all.py
5 years ago
70d00f2361
Tools: generate_manifest for KakuteF7Mini
5 years ago
e813d349ba
Tools: added bin format as valid firmware
5 years ago
29e8d17e2c
Tools: show test timings in CI output
5 years ago
cebe4eefa5
Tools: Remove gcc 4.9 from CI prereqs
5 years ago
c545171cec
Tools: fixed compiler path for autotest
5 years ago
fc16c5c2ae
Tools: align ci gcc with environment gcc v6 on arm
5 years ago
704407118b
Tools: use https:// scheme for ardupilot URLs
5 years ago
d7018a2ba0
Tools: switch to https URL for firmware
5 years ago
dd4ec08ec8
Tools: removed old wordpress update of params
5 years ago
36ea023e8d
Tools: added H7 info in uploader
...
and don't mention 1M flaw unless family is vulnerable to it
5 years ago
8f99262ffe
Tools: CI: install MAVProxy from source rather than using pip
...
Trying to get correct version of pymavlink (i.e. the one with messages
references in our mavlink repository)
As-is, if there is a pymavlink release after the one references in the
ardupilot repo, we don't pick up any new messages in the Python
bindings.
5 years ago
ee1f919244
Tools: do recursive submodule update when installing pymavlink
5 years ago
1279c63ece
Tools: run-coverage: build unit-tests and examples with debug
5 years ago
db8c682a14
Tools: added f303-GPS to builds
5 years ago
cd98659abe
Tools: cope with location of AP_Periph in Tools directory
5 years ago
9a176526d7
Tools: include bin files on firmware server for AP_Periph
5 years ago
6f6a8d5d14
Tools: auto-build AP_Periph binaries
5 years ago
c5afc3ff99
Tools: use crc_crc32() in app descriptor
5 years ago
5cda8b4a4f
Tools: updated AP_Periph CI and docs
...
target is now f103-GPS
5 years ago
16c9649ced
Tools: bootloader and binary build for Kakute F7 mini
5 years ago
c19d31d0c3
Tools: autobuild Pixhawk1-1M
5 years ago
073248eca5
Tools: autotest: remove vestiges of waf-run coverage
5 years ago
f5364e5efa
Tools: added script for creating apj file from *.bin
...
useful when you have a binary firmware and want to be able to upload
it with uploader.py
5 years ago
d8fb003cc2
Tools: add entry for running unit tests to build_ci.sh
5 years ago
642935fd43
Tools: random Python cleanups based on lgtm analysis
5 years ago
cefd30a086
travis: run balancebot tests as part of CI
5 years ago
84b035692f
Tools: added --no-bl option to configure_all.py
5 years ago
Peter Barker
Andrew Tridgell
Andy Piper
Pierre Kancir
CUAVcaijie
Michel Pastor
Michael du Breuil