Mirrors/u-boot
2
0
Fork 0
mirror of https://github.com/AsahiLinux/u-boot synced 2024-11-10 15:14:43 +00:00
Code Issues Projects Releases Packages Wiki Activity
u-boot/.travis.yml

670 lines
24 KiB
YAML
Raw Normal View History

SPDX: Convert all of our single license tags to Linux Kernel style When U-Boot started using SPDX tags we were among the early adopters and there weren't a lot of other examples to borrow from. So we picked the area of the file that usually had a full license text and replaced it with an appropriate SPDX-License-Identifier: entry. Since then, the Linux Kernel has adopted SPDX tags and they place it as the very first line in a file (except where shebangs are used, then it's second line) and with slightly different comment styles than us. In part due to community overlap, in part due to better tag visibility and in part for other minor reasons, switch over to that style. This commit changes all instances where we have a single declared license in the tag as both the before and after are identical in tag contents. There's also a few places where I found we did not have a tag and have introduced one. Signed-off-by: Tom Rini <trini@konsulko.com>
2018-05-06 21:58:06 +00:00
# SPDX-License-Identifier: GPL-2.0+
.travis.yml: build u-boot on travis-ci Goal: - building all variants of U-Boot with multiple configurations - code quality checks and metrics - https://travis-ci.org/u-boot/u-boot/builds
2014-11-19 14:26:18 +00:00
# Copyright Roger Meier <r.meier@siemens.com>
# build U-Boot on Travis CI - https://travis-ci.org/
travis-ci: Switch to Ubuntu 14.04 'Trusty Tahr' In order to make other various improvements, update to the latest environment travis-ci supports. Signed-off-by: Tom Rini <trini@konsulko.com> Acked-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Heiko Schocher <hs@denx.de>
2016-10-20 15:03:19 +00:00
sudo: required
travis.yml: Switch to bionic for the host distribution To match what we're doing in GitLab, move to 'bionic' for these builds as well. Signed-off-by: Tom Rini <trini@konsulko.com>
2019-10-08 12:39:26 +00:00
dist: bionic
.travis.yml: explicitly request sudo Without this, builds default to using new Travis CI infra-structure which does no allow sudo. The builds need sudo in order to install the ELDK compilers. Consequently, almost all builds fail without this. I suspect that existing Travis CI users have not noticed this because their accounts or builds have been grand-fathered into backwards- compatible default settings, whereas I just set up a new build from scratch and received new default settings. Cc: Wolfgang Denk <wd@denx.de> Cc: Heiko Schocher <hs@denx.de> Cc: Tom Rini <trini@ti.com> Cc: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Cc: Andreas Färber <afaerber@suse.de> Signed-off-by: Stephen Warren <swarren@nvidia.com> Acked-by: Heiko Schocher <hs@denx.de>
2016-02-03 17:41:34 +00:00
.travis.yml: build u-boot on travis-ci Goal: - building all variants of U-Boot with multiple configurations - code quality checks and metrics - https://travis-ci.org/u-boot/u-boot/builds
2014-11-19 14:26:18 +00:00
language: c
.travis.yml: rework according to new travis-ci infra - install using addons.apt - remove MAKEALL - split mpc85xx boards - remove TEST_CONFIG_CMD, just info - fetch mips toolchain via buildman - remove --list-error-boards param - conditional script - use TOOLCHAIN instead of INSTALL_TOOLCHAIN - add aarch64 - enable notifications via email Signed-off-by: Roger Meier <r.meier@siemens.com> Cc: Wolfgang Denk <wd@denx.de> Cc: Heiko Schocher <hs@denx.de> Cc: Tom Rini <trini@ti.com> Cc: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Cc: Andreas Färber <afaerber@suse.de> Tested-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Acked-by: Heiko Schocher <hs@denx.de>
2016-01-25 19:22:41 +00:00
addons:
apt:
travis: Switch over to using LLVM-10 At this point LLVM-7 is rather old. Switch over to LLVM-10 to enable some amount of CI coverage with newer compilers. Signed-off-by: Tom Rini <trini@konsulko.com>
2020-02-12 22:14:57 +00:00
update: true
travis: Add sandbox/clang-7 support To make testing with clang support easier, add sandbox/clang-7 combination to our testing matrix. To facilitate this, switch to using the "sources" method that the travis.yml file supports to list additional repositories and add the official one for llvm-7. Due to buildman not supporting using clang at this time add logic to manually build a single sandbox configuration in the expected output directory so that we can still invoke all of our tests. Cc: Simon Glass <sjg@chromium.org> Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org>
2018-10-07 18:20:30 +00:00
sources:
travis: Switch over to using LLVM-10 At this point LLVM-7 is rather old. Switch over to LLVM-10 to enable some amount of CI coverage with newer compilers. Signed-off-by: Tom Rini <trini@konsulko.com>
2020-02-12 22:14:57 +00:00
- sourceline: 'deb http://apt.llvm.org/bionic/ llvm-toolchain-bionic-10 main'
key_url: 'https://apt.llvm.org/llvm-snapshot.gpg.key'
.travis.yml: rework according to new travis-ci infra - install using addons.apt - remove MAKEALL - split mpc85xx boards - remove TEST_CONFIG_CMD, just info - fetch mips toolchain via buildman - remove --list-error-boards param - conditional script - use TOOLCHAIN instead of INSTALL_TOOLCHAIN - add aarch64 - enable notifications via email Signed-off-by: Roger Meier <r.meier@siemens.com> Cc: Wolfgang Denk <wd@denx.de> Cc: Heiko Schocher <hs@denx.de> Cc: Tom Rini <trini@ti.com> Cc: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Cc: Andreas Färber <afaerber@suse.de> Tested-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Acked-by: Heiko Schocher <hs@denx.de>
2016-01-25 19:22:41 +00:00
packages:
travis: Replace pre-built ARM/ARM64 GRUB images with the one built from source As of today travis uses the pre-built GRUB ARM/ARM64 images from opensuse. But azure/gitlab are using images built from GRUB 2.04 source. This updates travis to build GRUB ARM/ARM64 UEFI targets from source, to keep in sync with azure/gitlab. Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
2020-03-28 14:25:25 +00:00
- autopoint
.travis.yml: rework according to new travis-ci infra - install using addons.apt - remove MAKEALL - split mpc85xx boards - remove TEST_CONFIG_CMD, just info - fetch mips toolchain via buildman - remove --list-error-boards param - conditional script - use TOOLCHAIN instead of INSTALL_TOOLCHAIN - add aarch64 - enable notifications via email Signed-off-by: Roger Meier <r.meier@siemens.com> Cc: Wolfgang Denk <wd@denx.de> Cc: Heiko Schocher <hs@denx.de> Cc: Tom Rini <trini@ti.com> Cc: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Cc: Andreas Färber <afaerber@suse.de> Tested-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Acked-by: Heiko Schocher <hs@denx.de>
2016-01-25 19:22:41 +00:00
- cppcheck
- sloccount
- sparse
- bc
- build-essential
sandbox: sdl: Move to use SDL2 Sandbox currently uses SDL1.2. SDL2 has been around for quite a while and is widely supported. It has a number of useful features. It seems appropriate to move sandbox over. Update the code to use SDL2 instead of SDL1.2. Signed-off-by: Simon Glass <sjg@chromium.org>
2020-02-03 14:36:12 +00:00
- libsdl2-dev
Enable test/py for sandbox in Travis CI This provides runtime test coverage in Travis, in addition to the existing build coverage. Signed-off-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Roger Meier <r.meier@siemens.com> Reviewed-by: Heiko Schocher <hs@denx.de> Acked-by: Simon Glass <sjg@chromium.org>
2016-02-09 01:23:35 +00:00
- python
travis: Add python3-sphinx to the package list In order to build htmldocs we need sphinx-build which comes from python3-sphinx. Signed-off-by: Tom Rini <trini@konsulko.com>
2020-02-24 20:10:36 +00:00
- python3-sphinx
gitlab/travis: Rework how and when we use virtualenv in order to use python3 As things stand today, we have tools that CI requires where "python" must be "python2". We need to use a virtualenv and pip in order to ensure that our pytest tests can be run. Rework things slightly so that: - On Travis-CI, we install python-pyelftools for the platforms that require pyelftools to be installed. - On GitLab-CI, we move to a newer base image that includes python3-pip and continue to use a virtualenv per job that needs it, for the correct set of packages. Reviewed-by: Simon Glass <sjg@chromium.org> Tested-by: Stephen Warren <swarren@nvidia.com> Tested-by: Simon Glass <sjg@chromium.org> [on sandbox] Signed-off-by: Tom Rini <trini@konsulko.com>
2019-10-24 15:59:27 +00:00
- python3-virtualenv
- python3-pip
travis-ci: Add swig and libpython-dev to the package list As part of 1905c8fc711a we introduced failures depending on if swig and libpython-dev are installed or not. To provide coverage for this are of code in the future ensure we have these packages installed. Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Heiko Schocher <hs@denx.de>
2017-01-23 22:40:22 +00:00
- swig
- libpython-dev
travis-ci: Update toolchain and buildman usage - Drop the 'cache' line, travis-ci says to not cache apt packages (and does not). - Get the Ubuntu provided toolchain for ARM and PowerPC. - Add more toolchain options that buildman can fetch. Signed-off-by: Tom Rini <trini@konsulko.com> Acked-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Heiko Schocher <hs@denx.de>
2016-10-20 15:08:26 +00:00
- iasl
travis: Add efi_loader grub2 test We have all the building blocks now to run arbitrary efi applications in travis. The most important one out there is grub2, so let's add a simple test to verify that grub2 still comes up. Signed-off-by: Alexander Graf <agraf@suse.de>
2016-11-18 12:18:00 +00:00
- grub-efi-ia32-bin
travis: Generate grub_x64.efi for qemu-x86_64 grub_x86.efi is for 32-bit QEMU. Generate the 64-bit one. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
2018-10-14 03:52:12 +00:00
- grub-efi-amd64-bin
travis: Add efi_loader grub2 test We have all the building blocks now to run arbitrary efi applications in travis. The most important one out there is grub2, so let's add a simple test to verify that grub2 still comes up. Signed-off-by: Alexander Graf <agraf@suse.de>
2016-11-18 12:18:00 +00:00
- rpm2cpio
- wget
dtc: Switch to building and using our own dtc unless provided This makes us act like the Linux Kernel does and allow for dtc to be provided externally but otherwise we use the version of dtc that is included in the sources. This in turn means that we can drop the checkdtc logic. We select DTC in the cases where we will need the dtc tool provided. Signed-off-by: Tom Rini <trini@konsulko.com>
2017-09-23 17:00:57 +00:00
- device-tree-compiler
.travis.yml: Add lzop We need lzop now in order to make some FIT images that use LZO compression on the contents. Signed-off-by: Tom Rini <trini@konsulko.com>
2018-03-14 18:02:49 +00:00
- lzop
binman: Support compressed entries Add support for compressing blob entries. This can help reduce image sizes for many types of data. It requires that the firmware be able to decompress the data at run-time. Signed-off-by: Simon Glass <sjg@chromium.org>
2018-09-14 10:57:26 +00:00
- liblz4-tool
binman: Add a utility library for coreboot CBFS Coreboot uses a simple flash-based filesystem called Coreboot Filesystem (CBFS) to organise files used during boot. This allows files to be named and their position in the flash to be set. It has special features for dealing with x86 devices which typically memory-map their SPI flash to the top of 32-bit address space and need a 'boot block' ending there. Create a library to help create and read CBFS files. This includes a writer class, a reader class and associated other helpers. Only a subset of features are currently supported. Signed-off-by: Simon Glass <sjg@chromium.org>
2019-07-08 19:18:52 +00:00
- lzma-alone
travis: Add sandbox/clang-7 support To make testing with clang support easier, add sandbox/clang-7 combination to our testing matrix. To facilitate this, switch to using the "sources" method that the travis.yml file supports to list additional repositories and add the official one for llvm-7. Due to buildman not supporting using clang at this time add logic to manually build a single sandbox configuration in the expected output directory so that we can still invoke all of our tests. Cc: Simon Glass <sjg@chromium.org> Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org>
2018-10-07 18:20:30 +00:00
- libisl15
travis: Switch over to using LLVM-10 At this point LLVM-7 is rather old. Switch over to LLVM-10 to enable some amount of CI coverage with newer compilers. Signed-off-by: Tom Rini <trini@konsulko.com>
2020-02-12 22:14:57 +00:00
- clang-10
travis: Add srecord package At least MIPS Boston currently uses srec_cat tool to fiddle with srecords. There will be other platforms coming, so install the tool to prevent build problems. Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com> Cc: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Cc: Michal Simek <michal.simek@xilinx.com> Cc: Tom Rini <trini@konsulko.com>
2019-03-14 00:01:24 +00:00
- srecord
travis: build HTML docs Several patches delivered incorrect restructured text as documentation. We should be able to discover this in Travis CI. Provide a build step for 'make htmldocs'. Add required package graphviz. Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
2020-02-21 17:24:00 +00:00
- graphviz
travis: add packages for UEFI secure boot test Pytest for UEFI secure boot will use several host commands. In particular, Test setup relies on efitools, whose version must be v1.5.2 or later. So fetch a new version of deb package directly. Please note it has a dependency on mtools, which must also be installed along wih efitools. In addition, the path, '/sbin', is added to PATH for use of sgdisk and mkfs. Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org> Reviewed-by: Tom Rini <trini@konsulko.com>
2020-04-14 02:51:53 +00:00
- coreutils
- util-linux
- dosfstools
- gdisk
- mount
- mtools
- openssl
- sbsigntool
Nokia RX-51: Add automated test for running RX-51 build in qemu This patch contains test/nokia_rx51_test.sh script which automatically download and compile all needed tools in local temporary directory to generate a simple MTD images for booting Maemo kernel image by U-Boot from RAM, eMMC and OneNAND. MTD images are then run in virtual n900 machine provided by qemu-linaro project. This script does not need any special privileges, so it can be run as non-root nobody user. It can be used to check that U-Boot for Nokia N900 is not broken and can be successfully booted in emulator. Script is registered to .azure-pipelines.yml, .gitlab-ci.yml and .travis.yml so it would be automatically run on those CI services. Signed-off-by: Pali Rohár <pali@kernel.org>
2020-05-17 12:38:22 +00:00
- fakeroot
- mtd-utils
Travis: Add squashfs-tools So that the tests we now have for squashfs can run, add squashfs-tools for mksquashfs. Signed-off-by: Tom Rini <trini@konsulko.com>
2020-08-07 16:33:39 +00:00
- squashfs-tools
buildman: support newer gcc versions from kernel.org Add support for gcc versions 7.3.0, 6.4.0 and 4.9.4. Also use a regex for matching the tarball names. Some gcc versions use '-ARCH-' instead of '_ARCH-'. As part of this, we switch TravisCI to also using these toolchains for all platforms. Signed-off-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Signed-off-by: Tom Rini <trini@konsulko.com>
2018-05-10 11:15:53 +00:00
.travis.yml: build u-boot on travis-ci Goal: - building all variants of U-Boot with multiple configurations - code quality checks and metrics - https://travis-ci.org/u-boot/u-boot/builds
2014-11-19 14:26:18 +00:00
install:
travis-ci: Add test.py for various qemu platforms - Add a PPA for a more recent qemu (required for PowerPC to work) - Add tests to run test.py for various QEMU platforms. This relies on swarren's uboot-test-hooks repository to provide the abstractions. Acked-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Heiko Schocher <hs@denx.de> Signed-off-by: Tom Rini <trini@konsulko.com>
2016-10-20 15:26:40 +00:00
# Clone uboot-test-hooks
- git clone --depth=1 git://github.com/swarren/uboot-test-hooks.git /tmp/uboot-test-hooks
- ln -s travis-ci /tmp/uboot-test-hooks/bin/`hostname`
- ln -s travis-ci /tmp/uboot-test-hooks/py/`hostname`
.travis.yml: build u-boot on travis-ci Goal: - building all variants of U-Boot with multiple configurations - code quality checks and metrics - https://travis-ci.org/u-boot/u-boot/builds
2014-11-19 14:26:18 +00:00
# prepare buildman environment
travis-ci: Use = not : when writing ~/.buildman Travis CI seems to be confused when there's a colon in an echo command, and this is currently worked around using a variable that contains the text we want to echo. Use = syntax instead so that we can remove the work-around; it's rather confusing until you find out what it's for. Signed-off-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Heiko Schocher <hs@denx.de>
2016-10-26 17:05:31 +00:00
- echo -e "[toolchain]\nroot = /usr" > ~/.buildman
travis: Update ARC toolchain to 2019.09 Per Alexey Brodkin, this is the current toolchain we should use when building for ARC, update. Signed-off-by: Tom Rini <trini@konsulko.com>
2020-04-27 20:41:11 +00:00
- echo -e "arc = /tmp/arc_gnu_2019.09_prebuilt_uclibc_le_archs_linux_install" >> ~/.buildman
travis: Rework how we write the ~/.buildman file With python3 we're now tripping over a long-standing problem with how we add to the buildman file with some toolchains. We cannot have multiple toolchain-alias sections as that leads to a parse error. Signed-off-by: Tom Rini <trini@konsulko.com>
2019-11-05 15:44:16 +00:00
- echo -e "\n[toolchain-alias]\nsh = sh2" >> ~/.buildman
- echo -e "x86 = i386" >> ~/.buildman;
- echo -e "riscv = riscv64" >> ~/.buildman;
.travis.yml: build u-boot on travis-ci Goal: - building all variants of U-Boot with multiple configurations - code quality checks and metrics - https://travis-ci.org/u-boot/u-boot/builds
2014-11-19 14:26:18 +00:00
- cat ~/.buildman
travis.yml: Switch to bionic for the host distribution To match what we're doing in GitLab, move to 'bionic' for these builds as well. Signed-off-by: Tom Rini <trini@konsulko.com>
2019-10-08 12:39:26 +00:00
- grub-mkimage --prefix="" -o ~/grub_x86.efi -O i386-efi normal echo lsefimmap lsefi lsefisystab efinet tftp minicmd
- grub-mkimage --prefix="" -o ~/grub_x64.efi -O x86_64-efi normal echo lsefimmap lsefi lsefisystab efinet tftp minicmd
- wget http://mirrors.kernel.org/ubuntu/pool/main/m/mpfr4/libmpfr4_3.1.4-1_amd64.deb && sudo dpkg -i libmpfr4_3.1.4-1_amd64.deb && rm libmpfr4_3.1.4-1_amd64.deb
travis: add packages for UEFI secure boot test Pytest for UEFI secure boot will use several host commands. In particular, Test setup relies on efitools, whose version must be v1.5.2 or later. So fetch a new version of deb package directly. Please note it has a dependency on mtools, which must also be installed along wih efitools. In addition, the path, '/sbin', is added to PATH for use of sgdisk and mkfs. Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org> Reviewed-by: Tom Rini <trini@konsulko.com>
2020-04-14 02:51:53 +00:00
- wget http://mirrors.kernel.org/ubuntu/pool/universe/e/efitools/efitools_1.8.1-0ubuntu2_amd64.deb && sudo dpkg -i efitools_1.8.1-0ubuntu2_amd64.deb && rm efitools_1.8.1-0ubuntu2_amd64.deb
.travis.yml: build u-boot on travis-ci Goal: - building all variants of U-Boot with multiple configurations - code quality checks and metrics - https://travis-ci.org/u-boot/u-boot/builds
2014-11-19 14:26:18 +00:00
env:
global:
travis: add packages for UEFI secure boot test Pytest for UEFI secure boot will use several host commands. In particular, Test setup relies on efitools, whose version must be v1.5.2 or later. So fetch a new version of deb package directly. Please note it has a dependency on mtools, which must also be installed along wih efitools. In addition, the path, '/sbin', is added to PATH for use of sgdisk and mkfs. Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org> Reviewed-by: Tom Rini <trini@konsulko.com>
2020-04-14 02:51:53 +00:00
- PATH=/tmp/qemu-install/bin:/tmp/uboot-test-hooks/bin:/sbin:/usr/bin:/bin:/usr/local/bin
travis: Add python path for environments When running in travis-ci, we want to pass environment configuration to the tests. These reside in a path available through PYTHONPATH, so let's define that one to point to the unit test repo. Signed-off-by: Alexander Graf <agraf@suse.de> Reviewed-by: Tom Rini <trini@konsulko.com>
2016-11-17 17:31:04 +00:00
- PYTHONPATH=/tmp/uboot-test-hooks/py/travis-ci
.travis.yml: build u-boot on travis-ci Goal: - building all variants of U-Boot with multiple configurations - code quality checks and metrics - https://travis-ci.org/u-boot/u-boot/builds
2014-11-19 14:26:18 +00:00
- BUILD_DIR=build
- HOSTCC="cc"
- HOSTCXX="c++"
travis: Switch to QEMU v4.2.0 globally Given our tests in GitLab / Azure we can use QEMU v4.2.0 for all platforms now. Signed-off-by: Tom Rini <trini@konsulko.com>
2020-01-11 13:07:03 +00:00
- QEMU_VERSION="v4.2.0"
.travis.yml: build u-boot on travis-ci Goal: - building all variants of U-Boot with multiple configurations - code quality checks and metrics - https://travis-ci.org/u-boot/u-boot/builds
2014-11-19 14:26:18 +00:00
before_script:
.travis.yml: rework according to new travis-ci infra - install using addons.apt - remove MAKEALL - split mpc85xx boards - remove TEST_CONFIG_CMD, just info - fetch mips toolchain via buildman - remove --list-error-boards param - conditional script - use TOOLCHAIN instead of INSTALL_TOOLCHAIN - add aarch64 - enable notifications via email Signed-off-by: Roger Meier <r.meier@siemens.com> Cc: Wolfgang Denk <wd@denx.de> Cc: Heiko Schocher <hs@denx.de> Cc: Tom Rini <trini@ti.com> Cc: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Cc: Andreas Färber <afaerber@suse.de> Tested-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Acked-by: Heiko Schocher <hs@denx.de>
2016-01-25 19:22:41 +00:00
# install toolchains based on TOOLCHAIN} variable
- if [[ "${TOOLCHAIN}" == *m68k* ]]; then ./tools/buildman/buildman --fetch-arch m68k ; fi
travis-ci: Update toolchain and buildman usage - Drop the 'cache' line, travis-ci says to not cache apt packages (and does not). - Get the Ubuntu provided toolchain for ARM and PowerPC. - Add more toolchain options that buildman can fetch. Signed-off-by: Tom Rini <trini@konsulko.com> Acked-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Heiko Schocher <hs@denx.de>
2016-10-20 15:08:26 +00:00
- if [[ "${TOOLCHAIN}" == *microblaze* ]]; then ./tools/buildman/buildman --fetch-arch microblaze ; fi
.travis.yml: rework according to new travis-ci infra - install using addons.apt - remove MAKEALL - split mpc85xx boards - remove TEST_CONFIG_CMD, just info - fetch mips toolchain via buildman - remove --list-error-boards param - conditional script - use TOOLCHAIN instead of INSTALL_TOOLCHAIN - add aarch64 - enable notifications via email Signed-off-by: Roger Meier <r.meier@siemens.com> Cc: Wolfgang Denk <wd@denx.de> Cc: Heiko Schocher <hs@denx.de> Cc: Tom Rini <trini@ti.com> Cc: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Cc: Andreas Färber <afaerber@suse.de> Tested-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Acked-by: Heiko Schocher <hs@denx.de>
2016-01-25 19:22:41 +00:00
- if [[ "${TOOLCHAIN}" == *mips* ]]; then ./tools/buildman/buildman --fetch-arch mips ; fi
buildman: support newer gcc versions from kernel.org Add support for gcc versions 7.3.0, 6.4.0 and 4.9.4. Also use a regex for matching the tarball names. Some gcc versions use '-ARCH-' instead of '_ARCH-'. As part of this, we switch TravisCI to also using these toolchains for all platforms. Signed-off-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Signed-off-by: Tom Rini <trini@konsulko.com>
2018-05-10 11:15:53 +00:00
- if [[ "${TOOLCHAIN}" == *sh* ]]; then ./tools/buildman/buildman --fetch-arch sh2 ; fi
travis: Switch to i386 version toolchain for x86 Currently this uses x86_64 version toolchain for x86 build in travis-ci. Change it to i386 version to avoid updating the buildman toolchain path every time when the toolchain version number is changed, eg: from 7.3.0 to 8.1.0. Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
2018-10-08 23:53:54 +00:00
- if [[ "${TOOLCHAIN}" == *i386* ]]; then
./tools/buildman/buildman --fetch-arch i386;
travis-ci: centralize ~/.buildman editing Any time an x86 toolchain is used, we need to edit ~/.buildman to reference it. Move the editing logic into a central place so that it doesn't have to be duplicated everywhere that uses the x86 toolchain; future patches will add additional cases where it's used. It would be nice if we could unconditionally write all of ~/.buildman at once. Unfortunately, buildman fails if any toolchain mentioned in a toolchain-prefix entry doesn't exist, even if it doesn't need to use it for the current build. The sandbox/x86 build definition currently does nothing more than edit ~/.buildman; no builds are run. Fix this by not defining a custom script for this build, and hence preventing that stanza from replacing the default script. Signed-off-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Heiko Schocher <hs@denx.de>
2016-10-26 17:05:33 +00:00
fi
travisci: Add support for ARC Finally adding support for ARC boards in TravisCI. To build for ARC boards we need to install Synopsys prebuilt toolchain which we do here. Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com> Cc: Tom Rini <trini@konsulko.com> Reviewed-by: Tom Rini <trini@konsulko.com>
2017-04-21 10:35:43 +00:00
- if [[ "${TOOLCHAIN}" == arc ]]; then
travis: Update ARC toolchain to 2019.09 Per Alexey Brodkin, this is the current toolchain we should use when building for ARC, update. Signed-off-by: Tom Rini <trini@konsulko.com>
2020-04-27 20:41:11 +00:00
wget https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain/releases/download/arc-2019.09-release/arc_gnu_2019.09_prebuilt_uclibc_le_archs_linux_install.tar.gz &&
tar -C /tmp -xf arc_gnu_2019.09_prebuilt_uclibc_le_archs_linux_install.tar.gz;
travisci: Add support for ARC Finally adding support for ARC boards in TravisCI. To build for ARC boards we need to install Synopsys prebuilt toolchain which we do here. Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com> Cc: Tom Rini <trini@konsulko.com> Reviewed-by: Tom Rini <trini@konsulko.com>
2017-04-21 10:35:43 +00:00
fi
.travis.yml: Support nds32 prebuilt toolchain Download nds32 prebuild toolchain from github which is base on gcc 8.0.1 version for regression. Signed-off-by: Rick Chen <rick@andestech.com> Cc: Greentime Hu <greentime@andestech.com>
2019-01-14 05:36:15 +00:00
- if [[ "${TOOLCHAIN}" == "nds32" ]]; then
wget https://github.com/vincentzwc/prebuilt-nds32-toolchain/releases/download/20180521/nds32le-linux-glibc-v3-upstream.tar.gz &&
tar -C /tmp -xf nds32le-linux-glibc-v3-upstream.tar.gz &&
echo -e "\n[toolchain-prefix]\nnds32 = /tmp/nds32le-linux-glibc-v3-upstream/bin/nds32le-linux-" >> ~/.buildman;
fi
.travis.yml: download xtensa prebuilt toolchain xtensa toolchains are core-specific, so give full toolchain name and download corresponding prebuilt toolchain from the github release. Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
2018-02-07 23:30:01 +00:00
- if [[ "${TOOLCHAIN}" == *xtensa* ]]; then
wget https://github.com/foss-xtensa/toolchain/releases/download/2018.02/x86_64-2018.02-${TOOLCHAIN}.tar.gz &&
tar -C /tmp -xf x86_64-2018.02-${TOOLCHAIN}.tar.gz &&
echo -e "\n[toolchain-prefix]\nxtensa = /tmp/2018.02/${TOOLCHAIN}/bin/${TOOLCHAIN}-" >> ~/.buildman;
fi
travis-ci: Switch over to Linaro gcc-6.3.1 toolchains for ARM Linaro provides a number of pre-built GCC toolchains for both 32 and 64bit ARM. Switch to their 2017.02 release of gcc-6.3.1 for both. Cc: Koen Kooi <koen.kooi@linaro.org> Signed-off-by: Tom Rini <trini@konsulko.com>
2017-04-14 23:47:51 +00:00
# If TOOLCHAIN is unset, we're on some flavour of ARM.
- if [[ "${TOOLCHAIN}" == "" ]]; then
buildman: support newer gcc versions from kernel.org Add support for gcc versions 7.3.0, 6.4.0 and 4.9.4. Also use a regex for matching the tarball names. Some gcc versions use '-ARCH-' instead of '_ARCH-'. As part of this, we switch TravisCI to also using these toolchains for all platforms. Signed-off-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Signed-off-by: Tom Rini <trini@konsulko.com>
2018-05-10 11:15:53 +00:00
./tools/buildman/buildman --fetch-arch arm &&
./tools/buildman/buildman --fetch-arch aarch64;
travis-ci: Switch over to Linaro gcc-6.3.1 toolchains for ARM Linaro provides a number of pre-built GCC toolchains for both 32 and 64bit ARM. Switch to their 2017.02 release of gcc-6.3.1 for both. Cc: Koen Kooi <koen.kooi@linaro.org> Signed-off-by: Tom Rini <trini@konsulko.com>
2017-04-14 23:47:51 +00:00
fi
buildman: support newer gcc versions from kernel.org Add support for gcc versions 7.3.0, 6.4.0 and 4.9.4. Also use a regex for matching the tarball names. Some gcc versions use '-ARCH-' instead of '_ARCH-'. As part of this, we switch TravisCI to also using these toolchains for all platforms. Signed-off-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Signed-off-by: Tom Rini <trini@konsulko.com>
2018-05-10 11:15:53 +00:00
- if [[ "${TOOLCHAIN}" == "powerpc" ]]; then ./tools/buildman/buildman --fetch-arch powerpc; fi
travis.yml: Support RISC-V Enable travis-ci support with a link having built. Signed-off-by: Chih-Mao Chen <cmchen@andestech.com> Signed-off-by: Rick Chen <rick@andestech.com> Signed-off-by: Rick Chen <rickchen36@gmail.com> Signed-off-by: Greentime Hu <green.hu@gmail.com>
2018-01-12 06:57:09 +00:00
- if [[ "${TOOLCHAIN}" == "riscv" ]]; then
travis: Build GRUB image for RISC-V 32-bit and 64-bit This adds the GRUB image build for RISC-V 32-bit and 64-bit. Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
2020-03-28 14:25:26 +00:00
./tools/buildman/buildman --fetch-arch riscv32 &&
travis: Use kernel.org pre-built toolchain for riscv This updates travis configuration to use kernel.org pre-built toolchain for riscv. Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
2018-08-30 13:17:06 +00:00
./tools/buildman/buildman --fetch-arch riscv64;
travis.yml: Support RISC-V Enable travis-ci support with a link having built. Signed-off-by: Chih-Mao Chen <cmchen@andestech.com> Signed-off-by: Rick Chen <rick@andestech.com> Signed-off-by: Rick Chen <rickchen36@gmail.com> Signed-off-by: Greentime Hu <green.hu@gmail.com>
2018-01-12 06:57:09 +00:00
fi
travis-ci: Switch to building QEMU First, there are a number of features in newer QEMU that will allow us to test a wider range of platforms, so we want to use at least v2.8.0. Second, making use of a PPA for QEMU fails from time to time. So we change to checking out and building a copy of QEMU when we know that we are going to use test.py and need QEMU to be installed. This adds around 4 minutes per test.py job that we run. Signed-off-by: Tom Rini <trini@konsulko.com>
2016-12-07 16:20:40 +00:00
- if [[ "${QEMU_TARGET}" != "" ]]; then
git clone git://git.qemu.org/qemu.git /tmp/qemu;
pushd /tmp/qemu;
git submodule update --init dtc &&
travis: Setup QEMU_VERSION as variable This change enables setting up specific Qemu version or sha1 for new targets which are added after (current) v3.0.0 version. This changes is preparation step for adding new Xilinx Versal Virt platform which was merge after v3.0.0. Signed-off-by: Michal Simek <michal.simek@xilinx.com> Reviewed-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Tom Rini <trini@konsulko.com>
2019-01-16 14:18:43 +00:00
git checkout ${QEMU_VERSION} &&
travis-ci: Switch to building QEMU First, there are a number of features in newer QEMU that will allow us to test a wider range of platforms, so we want to use at least v2.8.0. Second, making use of a PPA for QEMU fails from time to time. So we change to checking out and building a copy of QEMU when we know that we are going to use test.py and need QEMU to be installed. This adds around 4 minutes per test.py job that we run. Signed-off-by: Tom Rini <trini@konsulko.com>
2016-12-07 16:20:40 +00:00
./configure --prefix=/tmp/qemu-install --target-list=${QEMU_TARGET} &&
make -j4 all install;
popd;
fi
.travis.yml: build u-boot on travis-ci Goal: - building all variants of U-Boot with multiple configurations - code quality checks and metrics - https://travis-ci.org/u-boot/u-boot/builds
2014-11-19 14:26:18 +00:00
travis: Replace pre-built ARM/ARM64 GRUB images with the one built from source As of today travis uses the pre-built GRUB ARM/ARM64 images from opensuse. But azure/gitlab are using images built from GRUB 2.04 source. This updates travis to build GRUB ARM/ARM64 UEFI targets from source, to keep in sync with azure/gitlab. Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
2020-03-28 14:25:25 +00:00
# Build GRUB UEFI targets
- if [[ "${QEMU_TARGET}" == "arm-softmmu" ]]; then
git clone git://git.savannah.gnu.org/grub.git /tmp/grub &&
pushd /tmp/grub &&
git checkout grub-2.04 &&
./bootstrap &&
./configure --target=arm --with-platform=efi
CC=gcc
travis: Switch to gcc 9.2.0 Use gcc 9.2.0 to do the build testing. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Tom Rini <trini@konsulko.com>
2020-04-06 13:07:00 +00:00
TARGET_CC=~/.buildman-toolchains/gcc-9.2.0-nolibc/arm-linux-gnueabi/bin/arm-linux-gnueabi-gcc
TARGET_OBJCOPY=~/.buildman-toolchains/gcc-9.2.0-nolibc/arm-linux-gnueabi/bin/arm-linux-gnueabi-objcopy
TARGET_STRIP=~/.buildman-toolchains/gcc-9.2.0-nolibc/arm-linux-gnueabi/bin/arm-linux-gnueabi-strip
TARGET_NM=~/.buildman-toolchains/gcc-9.2.0-nolibc/arm-linux-gnueabi/bin/arm-linux-gnueabi-nm
TARGET_RANLIB=~/.buildman-toolchains/gcc-9.2.0-nolibc/arm-linux-gnueabi/bin/arm-linux-gnueabi-ranlib &&
travis: Replace pre-built ARM/ARM64 GRUB images with the one built from source As of today travis uses the pre-built GRUB ARM/ARM64 images from opensuse. But azure/gitlab are using images built from GRUB 2.04 source. This updates travis to build GRUB ARM/ARM64 UEFI targets from source, to keep in sync with azure/gitlab. Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
2020-03-28 14:25:25 +00:00
make -j4 &&
./grub-mkimage -O arm-efi -o ~/grub_arm.efi --prefix= -d
grub-core cat chain configfile echo efinet ext2 fat halt help linux
lsefisystab loadenv lvm minicmd normal part_msdos part_gpt reboot
search search_fs_file search_fs_uuid search_label serial sleep test
true &&
popd;
fi
- if [[ "${QEMU_TARGET}" == "aarch64-softmmu" ]]; then
git clone git://git.savannah.gnu.org/grub.git /tmp/grub &&
pushd /tmp/grub &&
git checkout grub-2.04 &&
./bootstrap &&
./configure --target=aarch64 --with-platform=efi
CC=gcc
travis: Switch to gcc 9.2.0 Use gcc 9.2.0 to do the build testing. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Tom Rini <trini@konsulko.com>
2020-04-06 13:07:00 +00:00
TARGET_CC=~/.buildman-toolchains/gcc-9.2.0-nolibc/aarch64-linux/bin/aarch64-linux-gcc
TARGET_OBJCOPY=~/.buildman-toolchains/gcc-9.2.0-nolibc/aarch64-linux/bin/aarch64-linux-objcopy
TARGET_STRIP=~/.buildman-toolchains/gcc-9.2.0-nolibc/aarch64-linux/bin/aarch64-linux-strip
TARGET_NM=~/.buildman-toolchains/gcc-9.2.0-nolibc/aarch64-linux/bin/aarch64-linux-nm
TARGET_RANLIB=~/.buildman-toolchains/gcc-9.2.0-nolibc/aarch64-linux/bin/aarch64-linux-ranlib &&
travis: Replace pre-built ARM/ARM64 GRUB images with the one built from source As of today travis uses the pre-built GRUB ARM/ARM64 images from opensuse. But azure/gitlab are using images built from GRUB 2.04 source. This updates travis to build GRUB ARM/ARM64 UEFI targets from source, to keep in sync with azure/gitlab. Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
2020-03-28 14:25:25 +00:00
make -j4 &&
./grub-mkimage -O arm64-efi -o ~/grub_arm64.efi --prefix= -d
grub-core cat chain configfile echo efinet ext2 fat halt help linux
lsefisystab loadenv lvm minicmd normal part_msdos part_gpt reboot
search search_fs_file search_fs_uuid search_label serial sleep test
true &&
popd;
fi
travis: Build GRUB image for RISC-V 32-bit and 64-bit This adds the GRUB image build for RISC-V 32-bit and 64-bit. Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
2020-03-28 14:25:26 +00:00
- if [[ "${QEMU_TARGET}" == "riscv32-softmmu" ]]; then
git clone git://git.savannah.gnu.org/grub.git /tmp/grub &&
pushd /tmp/grub &&
git checkout grub-2.04 &&
./bootstrap &&
./configure --target=riscv32 --with-platform=efi
CC=gcc
travis: Switch to gcc 9.2.0 Use gcc 9.2.0 to do the build testing. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Tom Rini <trini@konsulko.com>
2020-04-06 13:07:00 +00:00
TARGET_CC=~/.buildman-toolchains/gcc-9.2.0-nolibc/riscv32-linux/bin/riscv32-linux-gcc
TARGET_OBJCOPY=~/.buildman-toolchains/gcc-9.2.0-nolibc/riscv32-linux/bin/riscv32-linux-objcopy
TARGET_STRIP=~/.buildman-toolchains/gcc-9.2.0-nolibc/riscv32-linux/bin/riscv32-linux-strip
TARGET_NM=~/.buildman-toolchains/gcc-9.2.0-nolibc/riscv32-linux/bin/riscv32-linux-nm
TARGET_RANLIB=~/.buildman-toolchains/gcc-9.2.0-nolibc/riscv32-linux/bin/riscv32-linux-ranlib &&
travis: Build GRUB image for RISC-V 32-bit and 64-bit This adds the GRUB image build for RISC-V 32-bit and 64-bit. Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
2020-03-28 14:25:26 +00:00
make -j4 &&
./grub-mkimage -O riscv32-efi -o ~/grub_riscv32.efi --prefix= -d
grub-core cat chain configfile echo efinet ext2 fat halt help linux
lsefisystab loadenv lvm minicmd normal part_msdos part_gpt reboot
search search_fs_file search_fs_uuid search_label serial sleep test
true &&
popd;
fi
- if [[ "${QEMU_TARGET}" == "riscv64-softmmu" ]]; then
git clone git://git.savannah.gnu.org/grub.git /tmp/grub &&
pushd /tmp/grub &&
git checkout grub-2.04 &&
./bootstrap &&
./configure --target=riscv64 --with-platform=efi
CC=gcc
travis: Switch to gcc 9.2.0 Use gcc 9.2.0 to do the build testing. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Tom Rini <trini@konsulko.com>
2020-04-06 13:07:00 +00:00
TARGET_CC=~/.buildman-toolchains/gcc-9.2.0-nolibc/riscv64-linux/bin/riscv64-linux-gcc
TARGET_OBJCOPY=~/.buildman-toolchains/gcc-9.2.0-nolibc/riscv64-linux/bin/riscv64-linux-objcopy
TARGET_STRIP=~/.buildman-toolchains/gcc-9.2.0-nolibc/riscv64-linux/bin/riscv64-linux-strip
TARGET_NM=~/.buildman-toolchains/gcc-9.2.0-nolibc/riscv64-linux/bin/riscv64-linux-nm
TARGET_RANLIB=~/.buildman-toolchains/gcc-9.2.0-nolibc/riscv64-linux/bin/riscv64-linux-ranlib &&
travis: Build GRUB image for RISC-V 32-bit and 64-bit This adds the GRUB image build for RISC-V 32-bit and 64-bit. Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
2020-03-28 14:25:26 +00:00
make -j4 &&
./grub-mkimage -O riscv64-efi -o ~/grub_riscv64.efi --prefix= -d
grub-core cat chain configfile echo efinet ext2 fat halt help linux
lsefisystab loadenv lvm minicmd normal part_msdos part_gpt reboot
search search_fs_file search_fs_uuid search_label serial sleep test
true &&
popd;
fi
azure/gitlab/travis: Add RISC-V SPL testing This adds QEMU RISC-V 32/64 SPL testing. Unlike QEMU RISC-V 32/64, we test SPL running in M-mode and U-Boot proper running in S-mode, with a 4-core SMP configuration. Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
2020-03-28 14:25:29 +00:00
- if [[ "${TEST_PY_BD}" == "qemu-riscv32_spl" ]]; then
azure: gitlab: travis: Update OpenSBI used for RISC-V testing Change to use OpenSBI release v0.8 generic platform images for QEMU RISC-V CI testing for azure, gitlab and travis-ci. Signed-off-by: Bin Meng <bin.meng@windriver.com> Reviewed-by: Tom Rini <trini@konsulko.com>
2020-07-20 03:52:23 +00:00
wget -O - https://github.com/riscv/opensbi/releases/download/v0.8/opensbi-0.8-rv-bin.tar.xz | tar -C /tmp -xJ;
export OPENSBI=/tmp/opensbi-0.8-rv-bin/share/opensbi/ilp32/generic/firmware/fw_dynamic.bin;
azure/gitlab/travis: Add RISC-V SPL testing This adds QEMU RISC-V 32/64 SPL testing. Unlike QEMU RISC-V 32/64, we test SPL running in M-mode and U-Boot proper running in S-mode, with a 4-core SMP configuration. Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
2020-03-28 14:25:29 +00:00
fi
- if [[ "${TEST_PY_BD}" == "qemu-riscv64_spl" ]]; then
azure: gitlab: travis: Update OpenSBI used for RISC-V testing Change to use OpenSBI release v0.8 generic platform images for QEMU RISC-V CI testing for azure, gitlab and travis-ci. Signed-off-by: Bin Meng <bin.meng@windriver.com> Reviewed-by: Tom Rini <trini@konsulko.com>
2020-07-20 03:52:23 +00:00
wget -O - https://github.com/riscv/opensbi/releases/download/v0.8/opensbi-0.8-rv-bin.tar.xz | tar -C /tmp -xJ;
export OPENSBI=/tmp/opensbi-0.8-rv-bin/share/opensbi/lp64/generic/firmware/fw_dynamic.bin;
azure/gitlab/travis: Add RISC-V SPL testing This adds QEMU RISC-V 32/64 SPL testing. Unlike QEMU RISC-V 32/64, we test SPL running in M-mode and U-Boot proper running in S-mode, with a 4-core SMP configuration. Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
2020-03-28 14:25:29 +00:00
fi
travis: Replace pre-built ARM/ARM64 GRUB images with the one built from source As of today travis uses the pre-built GRUB ARM/ARM64 images from opensuse. But azure/gitlab are using images built from GRUB 2.04 source. This updates travis to build GRUB ARM/ARM64 UEFI targets from source, to keep in sync with azure/gitlab. Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
2020-03-28 14:25:25 +00:00
.travis.yml: build u-boot on travis-ci Goal: - building all variants of U-Boot with multiple configurations - code quality checks and metrics - https://travis-ci.org/u-boot/u-boot/builds
2014-11-19 14:26:18 +00:00
script:
travis-ci: compile with buildman when running test/py Use buildman to compile any U-Boot binary tested by test/py. This re-uses all the work done elsewhere to make buildman work within Travis-CI, in particular related to toolchain downloading and buildman config file creation. Signed-off-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Heiko Schocher <hs@denx.de>
2016-10-26 17:05:36 +00:00
# Comments must be outside the command strings below, or the Travis parser
# will get confused.
#
travis/gitlab/azure: Use -W to avoid warnings check We can use the -W flag to tell buildman to ignore warnings. Since we also have -E defined, compiler warnings are promoted to errors, so they will still cause a failure. But migration warnings of the form: ===================== WARNING ====================== This board does not use CONFIG_DM. CONFIG_DM will be compulsory starting with the v2020.01 release. Failure to update may result in board removal. See doc/driver-model/migration.rst for more info. will now be ignored. Signed-off-by: Simon Glass <sjg@chromium.org> Fixes: 329f5ef51d2 (travis.yml: run buildman with option -E) Reviewed-by: Tom Rini <trini@konsulko.com>
2020-03-18 15:42:57 +00:00
# If we've been asked to use clang only do one configuration.
#
travis: Split the building into two parts Buildman is used in two ways: - to build a selection of boards (with no testing) - to build a single board (and run pytest) The gitlab and azure scrips do this in separate places, but travis does not. To aid the refactoring process and keep the following patches in sync across all three environments, split the code out in travis as well. Use the buildman -w option for the single board. It is easier to understand since it specifies the output directory directly. Also it avoids needing to look at the internal .bm-work directory. This initially creates some duplicate code, but by the end of the series we have two completely different build paths with different arguments. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Tom Rini <trini@konsulko.com>
2020-03-18 15:42:49 +00:00
# Build a selection of boards if TEST_PY_BD is empty
travis/gitlab/azure: Drop BUILDMAN variable with test.py This is not needed in the test.py part of the config, now since we use the same name as the pytests. Drop BUILDMAN, retaining it only for the 'build' parts of the config, i.e. where we build multiple boards and don't run any tests. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Tom Rini <trini@konsulko.com>
2020-03-18 15:42:52 +00:00
- if [[ "${BUILDMAN}" != "" ]]; then
travis: Correct error checking when building boards At present if buildman reports an error, the travis build still succeeds. This is because the travis script does not stop when it sees errors; nor does it automatically return the exit code. Also the current error checking never triggers since 'ret' is not set. Fix this by setting 'ret' correctly. Signed-off-by: Simon Glass <sjg@chromium.org> Reported-by: Michal Simek <michal.simek@xilinx.com> Acked-by: Michal Simek <michal.simek@xilinx.com>
2020-04-19 23:02:32 +00:00
ret=0
tools/buildman/buildman -P -E -W ${BUILDMAN} ${OVERRIDE} || ret=$?;
travis/gitlab/azure: Use -W to avoid warnings check We can use the -W flag to tell buildman to ignore warnings. Since we also have -E defined, compiler warnings are promoted to errors, so they will still cause a failure. But migration warnings of the form: ===================== WARNING ====================== This board does not use CONFIG_DM. CONFIG_DM will be compulsory starting with the v2020.01 release. Failure to update may result in board removal. See doc/driver-model/migration.rst for more info. will now be ignored. Signed-off-by: Simon Glass <sjg@chromium.org> Fixes: 329f5ef51d2 (travis.yml: run buildman with option -E) Reviewed-by: Tom Rini <trini@konsulko.com>
2020-03-18 15:42:57 +00:00
if [[ $ret -ne 0 ]]; then
travis/gitlab/azure: Drop the buildman -d flag This has no effect since -S is not given also. Drop it. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Tom Rini <trini@konsulko.com>
2020-03-18 15:42:53 +00:00
tools/buildman/buildman -seP ${BUILDMAN};
travis-ci: use correct exit code on errors The phrase "if [ $? -ne 0 ]; then exit $?; fi" doesn't work correctly; by the time the "exit" statement runs, $? has already been over-written by the result of the [ command. Fix this by explicitly storing $? and then using that stored value in both the test and the error-case exit statement. This change also converts from textual comparison to integer comparison, since the exit code is an integer and there's no need to convert it to a string for comparison. Signed-off-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Heiko Schocher <hs@denx.de>
2016-10-26 17:05:32 +00:00
exit $ret;
fi;
.travis.yml: rework according to new travis-ci infra - install using addons.apt - remove MAKEALL - split mpc85xx boards - remove TEST_CONFIG_CMD, just info - fetch mips toolchain via buildman - remove --list-error-boards param - conditional script - use TOOLCHAIN instead of INSTALL_TOOLCHAIN - add aarch64 - enable notifications via email Signed-off-by: Roger Meier <r.meier@siemens.com> Cc: Wolfgang Denk <wd@denx.de> Cc: Heiko Schocher <hs@denx.de> Cc: Tom Rini <trini@ti.com> Cc: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Cc: Andreas Färber <afaerber@suse.de> Tested-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Acked-by: Heiko Schocher <hs@denx.de>
2016-01-25 19:22:41 +00:00
fi
travis: Split the building into two parts Buildman is used in two ways: - to build a selection of boards (with no testing) - to build a single board (and run pytest) The gitlab and azure scrips do this in separate places, but travis does not. To aid the refactoring process and keep the following patches in sync across all three environments, split the code out in travis as well. Use the buildman -w option for the single board. It is easier to understand since it specifies the output directory directly. Also it avoids needing to look at the internal .bm-work directory. This initially creates some duplicate code, but by the end of the series we have two completely different build paths with different arguments. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Tom Rini <trini@konsulko.com>
2020-03-18 15:42:49 +00:00
# Build just the one board needed for testing, if TEST_PY_BD is non-empty
travis/gitlab/azure: Use bash to avoid a_test_which_does_not_exist Bash allows for variables to expand only if non-empty: $ var=test $ echo ${var:+"$var"} test $ echo ${var:+"-k $var"} -k test $ var= $ echo ${var:+"-k $var"} Use this feature to avoid the workaround. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Tom Rini <trini@konsulko.com>
2020-03-18 15:42:56 +00:00
# Note: "${var:+"-k $var"}" expands to "" if $var is empty, "-k $var" if not
travis: Don't copy files into .bm-work/ At present if TEST_PY_BD is empty the script copies various files into a directory, to no purpose. This happens because UBOOT_TRAVIS_BUILD_DIR is set before TEST_PY_BD is tested. Move the 'if' to fix this. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Tom Rini <trini@konsulko.com>
2020-03-18 15:42:48 +00:00
- if [[ "${TEST_PY_BD}" != "" ]]; then
travis: Split the building into two parts Buildman is used in two ways: - to build a selection of boards (with no testing) - to build a single board (and run pytest) The gitlab and azure scrips do this in separate places, but travis does not. To aid the refactoring process and keep the following patches in sync across all three environments, split the code out in travis as well. Use the buildman -w option for the single board. It is easier to understand since it specifies the output directory directly. Also it avoids needing to look at the internal .bm-work directory. This initially creates some duplicate code, but by the end of the series we have two completely different build paths with different arguments. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Tom Rini <trini@konsulko.com>
2020-03-18 15:42:49 +00:00
export UBOOT_TRAVIS_BUILD_DIR=`cd .. && pwd`/${TEST_PY_BD};
travis: Don't copy files into .bm-work/ At present if TEST_PY_BD is empty the script copies various files into a directory, to no purpose. This happens because UBOOT_TRAVIS_BUILD_DIR is set before TEST_PY_BD is tested. Move the 'if' to fix this. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Tom Rini <trini@konsulko.com>
2020-03-18 15:42:48 +00:00
cp ~/grub_x86.efi $UBOOT_TRAVIS_BUILD_DIR/;
cp ~/grub_x64.efi $UBOOT_TRAVIS_BUILD_DIR/;
if [[ -e ~/grub_arm.efi ]]; then
cp ~/grub_arm.efi $UBOOT_TRAVIS_BUILD_DIR/;
fi;
if [[ -e ~/grub_arm64.efi ]]; then
cp ~/grub_arm64.efi $UBOOT_TRAVIS_BUILD_DIR/;
fi;
if [[ -e ~/grub_riscv32.efi ]]; then
cp ~/grub_riscv32.efi $UBOOT_TRAVIS_BUILD_DIR/;
fi;
if [[ -e ~/grub_riscv64.efi ]]; then
cp ~/grub_riscv64.efi $UBOOT_TRAVIS_BUILD_DIR/;
fi;
travis/gitlab/azure: Drop repeated buildman call with test.py It does not seem to be necessary to run buildman again to show errors, since any errors can be shown by the first invocation and there is only a single board being built. Update this to simplify the code, using the -e flag to make sure errors are shown. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Tom Rini <trini@konsulko.com>
2020-03-18 15:43:00 +00:00
tools/buildman/buildman -o ${UBOOT_TRAVIS_BUILD_DIR} -w -E -W -e
--board ${TEST_PY_BD} ${OVERRIDE} || exit;
gitlab/travis: Rework how and when we use virtualenv in order to use python3 As things stand today, we have tools that CI requires where "python" must be "python2". We need to use a virtualenv and pip in order to ensure that our pytest tests can be run. Rework things slightly so that: - On Travis-CI, we install python-pyelftools for the platforms that require pyelftools to be installed. - On GitLab-CI, we move to a newer base image that includes python3-pip and continue to use a virtualenv per job that needs it, for the correct set of packages. Reviewed-by: Simon Glass <sjg@chromium.org> Tested-by: Stephen Warren <swarren@nvidia.com> Tested-by: Simon Glass <sjg@chromium.org> [on sandbox] Signed-off-by: Tom Rini <trini@konsulko.com>
2019-10-24 15:59:27 +00:00
virtualenv -p /usr/bin/python3 /tmp/venv;
. /tmp/venv/bin/activate;
pip install -r test/py/requirements.txt;
CI: show skipped Python tests Call pytest3 with argument -ra to display the reason why Python tests are skipped. The -r flag displays a test summary info for each test. -ra eliminates this info for passed tests. Pros an cons were discussed in: https://lists.denx.de/pipermail/u-boot/2020-June/417090.html Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
2020-07-10 20:04:40 +00:00
./test/py/test.py -ra --bd ${TEST_PY_BD} ${TEST_PY_ID}
travis/gitlab/azure: Use bash to avoid a_test_which_does_not_exist Bash allows for variables to expand only if non-empty: $ var=test $ echo ${var:+"$var"} test $ echo ${var:+"-k $var"} -k test $ var= $ echo ${var:+"-k $var"} Use this feature to avoid the workaround. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Tom Rini <trini@konsulko.com>
2020-03-18 15:42:56 +00:00
${TEST_PY_TEST_SPEC:+"-k ${TEST_PY_TEST_SPEC}"}
travis/gitlab/azure: Simplify the exit code for test.py It seems unnecessary to read the exit code and then check it again. Drop this and just let the test.py provide the exit code directly. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Tom Rini <trini@konsulko.com>
2020-03-18 15:42:59 +00:00
--build-dir "$UBOOT_TRAVIS_BUILD_DIR" || exit;
travis/gitlab/azure: Ensure we use python3 always When running our tests there are some cases where as part of the Python 2.7 to Python 3.6 migration we didn't force Python 3.6 to be used as everything wasn't yet migrated. Now that everything is, make sure to tell virtualenv to use python3. In the case of Travis this is best done by making the tools test happen after the main tests so that it will already have been run in all cases, TEST_PY_TOOLS is a subset of TEST_PY_BD. Signed-off-by: Tom Rini <trini@konsulko.com>
2020-02-11 17:41:14 +00:00
if [[ -n "${TEST_PY_TOOLS}" ]]; then
export PYTHONPATH="${UBOOT_TRAVIS_BUILD_DIR}/scripts/dtc/pylibfdt";
export PATH="${UBOOT_TRAVIS_BUILD_DIR}/scripts/dtc:${PATH}";
travis: Install pyelftools via pip With the migration to python3 for all of our tests, we need to install pyelftools via pip now rather than the system tools as they will otherwise not be present in our virtualenv. Signed-off-by: Tom Rini <trini@konsulko.com> --- Changes in v2: Switch to pip
2020-07-27 15:11:27 +00:00
pip install pyelftools &&
travis/gitlab/azure: Ensure we use python3 always When running our tests there are some cases where as part of the Python 2.7 to Python 3.6 migration we didn't force Python 3.6 to be used as everything wasn't yet migrated. Now that everything is, make sure to tell virtualenv to use python3. In the case of Travis this is best done by making the tools test happen after the main tests so that it will already have been run in all cases, TEST_PY_TOOLS is a subset of TEST_PY_BD. Signed-off-by: Tom Rini <trini@konsulko.com>
2020-02-11 17:41:14 +00:00
./tools/binman/binman --toolpath ${UBOOT_TRAVIS_BUILD_DIR}/tools test &&
patman: Add a 'test' subcommand At present we use --test to indicate that tests should be run. It is better to use a subcommand for list, like binman. Change it and adjust the existing code to fit under a 'send' subcommand, the default. Give this subcommand the same default arguments as the others. Signed-off-by: Simon Glass <sjg@chromium.org>
2020-07-06 03:41:55 +00:00
./tools/patman/patman test &&
travis/gitlab/azure: Ensure we use python3 always When running our tests there are some cases where as part of the Python 2.7 to Python 3.6 migration we didn't force Python 3.6 to be used as everything wasn't yet migrated. Now that everything is, make sure to tell virtualenv to use python3. In the case of Travis this is best done by making the tools test happen after the main tests so that it will already have been run in all cases, TEST_PY_TOOLS is a subset of TEST_PY_BD. Signed-off-by: Tom Rini <trini@konsulko.com>
2020-02-11 17:41:14 +00:00
./tools/buildman/buildman -t &&
Azure / GitLab / Travis: Add Kconfig unit tests to a job The Kconfig language provides a unit test that can be run. As these require pytest to be installed and run very quickly, bundle them in to an existing CI job. Signed-off-by: Tom Rini <trini@konsulko.com>
2020-03-11 22:11:15 +00:00
./tools/dtoc/dtoc -t &&
make testconfig;
travis/gitlab/azure: Ensure we use python3 always When running our tests there are some cases where as part of the Python 2.7 to Python 3.6 migration we didn't force Python 3.6 to be used as everything wasn't yet migrated. Now that everything is, make sure to tell virtualenv to use python3. In the case of Travis this is best done by making the tools test happen after the main tests so that it will already have been run in all cases, TEST_PY_TOOLS is a subset of TEST_PY_BD. Signed-off-by: Tom Rini <trini@konsulko.com>
2020-02-11 17:41:14 +00:00
fi;
travis-ci: compile with buildman when running test/py Use buildman to compile any U-Boot binary tested by test/py. This re-uses all the work done elsewhere to make buildman work within Travis-CI, in particular related to toolchain downloading and buildman config file creation. Signed-off-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Heiko Schocher <hs@denx.de>
2016-10-26 17:05:36 +00:00
fi
.travis.yml: build u-boot on travis-ci Goal: - building all variants of U-Boot with multiple configurations - code quality checks and metrics - https://travis-ci.org/u-boot/u-boot/builds
2014-11-19 14:26:18 +00:00
matrix:
include:
# we need to build by vendor due to 50min time limit for builds
# each env setting here is a dedicated build
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "buildman arc"
env:
travisci: Add support for ARC Finally adding support for ARC boards in TravisCI. To build for ARC boards we need to install Synopsys prebuilt toolchain which we do here. Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com> Cc: Tom Rini <trini@konsulko.com> Reviewed-by: Tom Rini <trini@konsulko.com>
2017-04-21 10:35:43 +00:00
- BUILDMAN="arc"
TOOLCHAIN="arc"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "buildman arm11 arm7 arm920t arm946es"
env:
.travis.yml: Further optimizations - Xilinx aarch64 is caught in the general xilinx arm job, exclude from the general aarch64 job. - Give the generic aarch64 job a better name - Re-sort the PowerPC jobs so that we can complete them a bit quicker. Signed-off-by: Tom Rini <trini@konsulko.com>
2018-05-10 11:15:54 +00:00
- BUILDMAN="arm11 arm7 arm920t arm946es"
travis-ci: fix at91 missing boards Fix missing at91 boards and split the at91 in two categories: at91 arm v7 at91 arm926esj which are the two main cores for the at91 architecture. Signed-off-by: Eugen Hristev <eugen.hristev@microchip.com>
2019-04-01 11:04:03 +00:00
- name: "buildman arm926ejs (non-NXP,siemens,at91,kirkwood,spear)"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
env:
travis-ci: Try harder to build all ARM targets The way that we have things broken down currently allows for some combinations of vendor or CPU to not be built. To fix this, create a new catch-all job that excludes everything we've built elsewhere. For the sake of simplicity we are allowing for the possibility of some overlap between the vendor-based jobs and the CPU-based jobs. While we're in here, make a failed build provide the summary of failure. Signed-off-by: Tom Rini <trini@konsulko.com>
2016-11-05 23:34:49 +00:00
- JOB="arm926ejs"
travis-ci: fix at91 missing boards Fix missing at91 boards and split the at91 in two categories: at91 arm v7 at91 arm926esj which are the two main cores for the at91 architecture. Signed-off-by: Eugen Hristev <eugen.hristev@microchip.com>
2019-04-01 11:04:03 +00:00
BUILDMAN="arm926ejs -x freescale,siemens,at91,kirkwood,spear,omap"
- name: "buildman at91 (non arm v7)"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
env:
travis-ci: fix at91 missing boards Fix missing at91 boards and split the at91 in two categories: at91 arm v7 at91 arm926esj which are the two main cores for the at91 architecture. Signed-off-by: Eugen Hristev <eugen.hristev@microchip.com>
2019-04-01 11:04:03 +00:00
- BUILDMAN="at91 -x armv7"
- name: "buildman at91 (non arm926ejs)"
env:
- BUILDMAN="at91 -x arm926ejs"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "buildman boundary engicam toradex"
env:
- BUILDMAN="boundary engicam toradex"
travis: Exclude MIPS from the bcm job We don't need to pull in anything from the MIPS job so exclude that from the new bcm job and make it clear it's building only ARM. Signed-off-by: Tom Rini <trini@konsulko.com>
2019-10-13 15:21:56 +00:00
- name: "buildman ARM bcm"
travis: Split bcm SoCs into their own build job As both "catch-all" ARM jobs are nearing their time limit, move all of the bcm SoC boards into a single job. Signed-off-by: Tom Rini <trini@konsulko.com>
2019-10-09 15:01:06 +00:00
env:
travis: Exclude MIPS from the bcm job We don't need to pull in anything from the MIPS job so exclude that from the new bcm job and make it clear it's building only ARM. Signed-off-by: Tom Rini <trini@konsulko.com>
2019-10-13 15:21:56 +00:00
- BUILDMAN="bcm -x mips"
travis: rework NXP layerscape jobs remove from NXP arm32 all layerscape boards and build them instead in already existing layerscape jobs (which now not only build aarch64 boards) Signed-off-by: Heiko Schocher <hs@denx.de>
2019-11-22 10:17:29 +00:00
- name: "buildman NXP ARM32 (catch-all)"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
env:
travis: rework NXP layerscape jobs remove from NXP arm32 all layerscape boards and build them instead in already existing layerscape jobs (which now not only build aarch64 boards) Signed-off-by: Heiko Schocher <hs@denx.de>
2019-11-22 10:17:29 +00:00
- BUILDMAN="freescale -x powerpc,m68k,aarch64,ls101,ls102,ls104,ls108,ls20,lx216"
- name: "buildman NXP LS101x"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
env:
travis: rework NXP layerscape jobs remove from NXP arm32 all layerscape boards and build them instead in already existing layerscape jobs (which now not only build aarch64 boards) Signed-off-by: Heiko Schocher <hs@denx.de>
2019-11-22 10:17:29 +00:00
- BUILDMAN="freescale&ls101"
- name: "buildman NXP LS102x"
travis.yml: Add buildman support for NXP's LS1028 & LX2160 NXP's LS1028 and LX2160 platform build support added via buildman in travis.yml. Signed-off-by: Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>
2019-06-19 12:17:12 +00:00
env:
travis: rework NXP layerscape jobs remove from NXP arm32 all layerscape boards and build them instead in already existing layerscape jobs (which now not only build aarch64 boards) Signed-off-by: Heiko Schocher <hs@denx.de>
2019-11-22 10:17:29 +00:00
- BUILDMAN="freescale&ls102"
- name: "buildman NXP LS104x"
travis: Rework Freescale ARM jobs a bit - Split the AArch64 LS10xx and LS20xx builds into their own jobs, and then exclude only ls1/ls2 from the catch-all. This moves the S32V234 job (and future i.MX8*) to the catch-all. - Split spear out from arm926ejs and exclude freescale, not mx from that job. The older Freescale i.MX boards are caught by the catch-all job for Freescale but now we build the non-Freescale older i.MX platforms. Signed-off-by: Tom Rini <trini@konsulko.com>
2018-10-23 15:58:44 +00:00
env:
travis: rework NXP layerscape jobs remove from NXP arm32 all layerscape boards and build them instead in already existing layerscape jobs (which now not only build aarch64 boards) Signed-off-by: Heiko Schocher <hs@denx.de>
2019-11-22 10:17:29 +00:00
- BUILDMAN="freescale&ls104"
- name: "buildman NXP LS108x"
travis: Break up the NXP Layerscape jobs more The single job for all Layerscape 10xx platforms is close to, and sometimes exceeds the time limit for a single job configuration. Break this down into jobs for LS101x, LS104x and LS108x instead. While in here, in the name portion of these jobs, refer to them as NXP for ARM and not Freescale as they've been NXP for quite some time. Signed-off-by: Tom Rini <trini@konsulko.com>
2019-01-16 12:19:26 +00:00
env:
travis: rework NXP layerscape jobs remove from NXP arm32 all layerscape boards and build them instead in already existing layerscape jobs (which now not only build aarch64 boards) Signed-off-by: Heiko Schocher <hs@denx.de>
2019-11-22 10:17:29 +00:00
- BUILDMAN="freescale&ls108"
- name: "buildman NXP LS20xx"
travis: Break up the NXP Layerscape jobs more The single job for all Layerscape 10xx platforms is close to, and sometimes exceeds the time limit for a single job configuration. Break this down into jobs for LS101x, LS104x and LS108x instead. While in here, in the name portion of these jobs, refer to them as NXP for ARM and not Freescale as they've been NXP for quite some time. Signed-off-by: Tom Rini <trini@konsulko.com>
2019-01-16 12:19:26 +00:00
env:
travis: rework NXP layerscape jobs remove from NXP arm32 all layerscape boards and build them instead in already existing layerscape jobs (which now not only build aarch64 boards) Signed-off-by: Heiko Schocher <hs@denx.de>
2019-11-22 10:17:29 +00:00
- BUILDMAN="freescale&ls20"
- name: "buildman NXP LX216x"
travis.yml: Add buildman support for NXP's LS1028 & LX2160 NXP's LS1028 and LX2160 platform build support added via buildman in travis.yml. Signed-off-by: Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>
2019-06-19 12:17:12 +00:00
env:
travis: rework NXP layerscape jobs remove from NXP arm32 all layerscape boards and build them instead in already existing layerscape jobs (which now not only build aarch64 boards) Signed-off-by: Heiko Schocher <hs@denx.de>
2019-11-22 10:17:29 +00:00
- BUILDMAN="freescale&lx216"
travis: Split i.MX jobs a bit more - Split "tqc" and "technexion" out into their own jobs and exclude them from the catch-all jobs - Clarify the job labels a little more. Cc: Stefano Babic <sbabic@denx.de> Signed-off-by: Tom Rini <trini@konsulko.com> Acked-by: Stefano Babic <sbabic@denx.de>
2019-10-15 11:27:13 +00:00
- name: "buildman i.MX6 tqc"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
env:
travis: Split i.MX jobs a bit more - Split "tqc" and "technexion" out into their own jobs and exclude them from the catch-all jobs - Clarify the job labels a little more. Cc: Stefano Babic <sbabic@denx.de> Signed-off-by: Tom Rini <trini@konsulko.com> Acked-by: Stefano Babic <sbabic@denx.de>
2019-10-15 11:27:13 +00:00
- BUILDMAN="mx6&tqc"
- name: "buildman i.MX6 (catch-all)"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
env:
travis: Split i.MX jobs a bit more - Split "tqc" and "technexion" out into their own jobs and exclude them from the catch-all jobs - Clarify the job labels a little more. Cc: Stefano Babic <sbabic@denx.de> Signed-off-by: Tom Rini <trini@konsulko.com> Acked-by: Stefano Babic <sbabic@denx.de>
2019-10-15 11:27:13 +00:00
- BUILDMAN="mx6 -x boundary,engicam,freescale,technexion,toradex,tqc"
- name: "buildman i.MX (non-i.MX6 catch-all)"
env:
- BUILDMAN="mx -x freescale,mx6,toradex,technexion"
travis: Move keystone 3 (k3) boards into the k2 job Build the keystone 3 platforms with the keystone 2 platforms, in order to get back more room in the "catch-all" build jobs. Signed-off-by: Tom Rini <trini@konsulko.com>
2019-10-09 15:02:21 +00:00
- name: "buildman keystone 2/3"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
env:
travis: Move keystone 3 (k3) boards into the k2 job Build the keystone 3 platforms with the keystone 2 platforms, in order to get back more room in the "catch-all" build jobs. Signed-off-by: Tom Rini <trini@konsulko.com>
2019-10-09 15:02:21 +00:00
- BUILDMAN="k2 k3"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "buildman samsung socfpga"
env:
.travis.yml: Further optimizations - Xilinx aarch64 is caught in the general xilinx arm job, exclude from the general aarch64 job. - Give the generic aarch64 job a better name - Re-sort the PowerPC jobs so that we can complete them a bit quicker. Signed-off-by: Tom Rini <trini@konsulko.com>
2018-05-10 11:15:54 +00:00
- BUILDMAN="samsung socfpga"
travis: Rework Freescale ARM jobs a bit - Split the AArch64 LS10xx and LS20xx builds into their own jobs, and then exclude only ls1/ls2 from the catch-all. This moves the S32V234 job (and future i.MX8*) to the catch-all. - Split spear out from arm926ejs and exclude freescale, not mx from that job. The older Freescale i.MX boards are caught by the catch-all job for Freescale but now we build the non-Freescale older i.MX platforms. Signed-off-by: Tom Rini <trini@konsulko.com>
2018-10-23 15:58:44 +00:00
- name: "buildman spear"
env:
- BUILDMAN="spear"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "buildman sun4i"
env:
travis-ci: Try harder to build all ARM targets The way that we have things broken down currently allows for some combinations of vendor or CPU to not be built. To fix this, create a new catch-all job that excludes everything we've built elsewhere. For the sake of simplicity we are allowing for the possibility of some overlap between the vendor-based jobs and the CPU-based jobs. While we're in here, make a failed build provide the summary of failure. Signed-off-by: Tom Rini <trini@konsulko.com>
2016-11-05 23:34:49 +00:00
- BUILDMAN="sun4i"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "buildman sun5i"
env:
travis-ci: Try harder to build all ARM targets The way that we have things broken down currently allows for some combinations of vendor or CPU to not be built. To fix this, create a new catch-all job that excludes everything we've built elsewhere. For the sake of simplicity we are allowing for the possibility of some overlap between the vendor-based jobs and the CPU-based jobs. While we're in here, make a failed build provide the summary of failure. Signed-off-by: Tom Rini <trini@konsulko.com>
2016-11-05 23:34:49 +00:00
- BUILDMAN="sun5i"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "buildman sun6i"
env:
travis-ci: Try harder to build all ARM targets The way that we have things broken down currently allows for some combinations of vendor or CPU to not be built. To fix this, create a new catch-all job that excludes everything we've built elsewhere. For the sake of simplicity we are allowing for the possibility of some overlap between the vendor-based jobs and the CPU-based jobs. While we're in here, make a failed build provide the summary of failure. Signed-off-by: Tom Rini <trini@konsulko.com>
2016-11-05 23:34:49 +00:00
- BUILDMAN="sun6i"
.travis.yml: Fix typo in sun7i job description 'builman' -> 'buildman' Signed-off-by: Tuomas Tynkkynen <tuomas.tynkkynen@iki.fi>
2018-09-07 21:53:18 +00:00
- name: "buildman sun7i"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
env:
travis-ci: Try harder to build all ARM targets The way that we have things broken down currently allows for some combinations of vendor or CPU to not be built. To fix this, create a new catch-all job that excludes everything we've built elsewhere. For the sake of simplicity we are allowing for the possibility of some overlap between the vendor-based jobs and the CPU-based jobs. While we're in here, make a failed build provide the summary of failure. Signed-off-by: Tom Rini <trini@konsulko.com>
2016-11-05 23:34:49 +00:00
- BUILDMAN="sun7i"
travis: Split sun8i in to two jobs Split the 32bit and 64bit platforms into separate jobs, to avoid them taking too long to build overall. Cc: Jagan Teki <jagan@amarulasolutions.com> Signed-off-by: Tom Rini <trini@konsulko.com>
2019-10-15 11:27:14 +00:00
- name: "buildman 64bit sun8i"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
env:
travis: move orangepi to vendor job move orangepi builds into a new job, and exclude orangepi builds from sunxi and rockchip jobs. Signed-off-by: Heiko Schocher <hs@denx.de> Reviewed-by: Tom Rini <trini@konsulko.com>
2019-11-21 05:50:12 +00:00
- BUILDMAN="sun8i&aarch64 -x orangepi"
travis: Split sun8i in to two jobs Split the 32bit and 64bit platforms into separate jobs, to avoid them taking too long to build overall. Cc: Jagan Teki <jagan@amarulasolutions.com> Signed-off-by: Tom Rini <trini@konsulko.com>
2019-10-15 11:27:14 +00:00
- name: "buildman 32bit sun8i"
env:
travis: move orangepi to vendor job move orangepi builds into a new job, and exclude orangepi builds from sunxi and rockchip jobs. Signed-off-by: Heiko Schocher <hs@denx.de> Reviewed-by: Tom Rini <trini@konsulko.com>
2019-11-21 05:50:12 +00:00
- BUILDMAN="sun8i&armv7 -x orangepi"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "buildman sun9i"
env:
travis-ci: Try harder to build all ARM targets The way that we have things broken down currently allows for some combinations of vendor or CPU to not be built. To fix this, create a new catch-all job that excludes everything we've built elsewhere. For the sake of simplicity we are allowing for the possibility of some overlap between the vendor-based jobs and the CPU-based jobs. While we're in here, make a failed build provide the summary of failure. Signed-off-by: Tom Rini <trini@konsulko.com>
2016-11-05 23:34:49 +00:00
- BUILDMAN="sun9i"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "buildman sun50i"
env:
travis: move orangepi to vendor job move orangepi builds into a new job, and exclude orangepi builds from sunxi and rockchip jobs. Signed-off-by: Heiko Schocher <hs@denx.de> Reviewed-by: Tom Rini <trini@konsulko.com>
2019-11-21 05:50:12 +00:00
- BUILDMAN="sun50i -x orangepi"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "buildman catch-all ARM"
env:
Azure/Travis: Re-sync jobs and clarify exclusions We keep both of these jobs in sync as much as possible even when the primary motivation is to keep Travis from exceeding the build time limit there. With that in mind: - Use "rk" not "rockchip" to get all Rockchip SoC platforms in one job, rather than just all Rockchip vendor platforms. - The NXP LX216* SoCs have their own job, exclude them from the AArch64 generic job. - SoCFPGA SoCs have their own job, exclude them from the AArch64 generic job. Signed-off-by: Tom Rini <trini@konsulko.com>
2020-03-09 17:01:57 +00:00
- BUILDMAN="arm -x arm11,arm7,arm9,aarch64,at91,bcm,freescale,kirkwood,mvebu,siemens,tegra,uniphier,mx,samsung,sunxi,am33xx,omap,rk,toradex,socfpga,k2,k3,zynq"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "buildman sandbox x86"
env:
.travis.yml: rework according to new travis-ci infra - install using addons.apt - remove MAKEALL - split mpc85xx boards - remove TEST_CONFIG_CMD, just info - fetch mips toolchain via buildman - remove --list-error-boards param - conditional script - use TOOLCHAIN instead of INSTALL_TOOLCHAIN - add aarch64 - enable notifications via email Signed-off-by: Roger Meier <r.meier@siemens.com> Cc: Wolfgang Denk <wd@denx.de> Cc: Heiko Schocher <hs@denx.de> Cc: Tom Rini <trini@ti.com> Cc: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Cc: Andreas Färber <afaerber@suse.de> Tested-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Acked-by: Heiko Schocher <hs@denx.de>
2016-01-25 19:22:41 +00:00
- BUILDMAN="sandbox x86"
travis: Switch to i386 version toolchain for x86 Currently this uses x86_64 version toolchain for x86 build in travis-ci. Change it to i386 version to avoid updating the buildman toolchain path every time when the toolchain version number is changed, eg: from 7.3.0 to 8.1.0. Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
2018-10-08 23:53:54 +00:00
TOOLCHAIN="i386"
travis: Split i.MX jobs a bit more - Split "tqc" and "technexion" out into their own jobs and exclude them from the catch-all jobs - Clarify the job labels a little more. Cc: Stefano Babic <sbabic@denx.de> Signed-off-by: Tom Rini <trini@konsulko.com> Acked-by: Stefano Babic <sbabic@denx.de>
2019-10-15 11:27:13 +00:00
- name: "buildman technexion"
env:
- BUILDMAN="technexion"
arm: kirkwood: openrd: Mark openrd boards as maintained again With the latest size increase of the openrd boards, they all compile clean again. Let's mark them as maintained again and add the Travis job. Please note that I can only compile-test these targets as I don't have access to one of those boards. Signed-off-by: Stefan Roese <sr@denx.de> Cc: Albert ARIBAUD <albert-u-boot@aribaud.net> Cc: Vagrant Cascadian <vagrant@debian.org> Cc: Chris Packham <judge.packham@gmail.com> Cc: Tom Rini <trini@konsulko.com>
2019-04-25 09:53:18 +00:00
- name: "buildman kirkwood"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
env:
arm: kirkwood: openrd: Mark openrd boards as maintained again With the latest size increase of the openrd boards, they all compile clean again. Let's mark them as maintained again and add the Travis job. Please note that I can only compile-test these targets as I don't have access to one of those boards. Signed-off-by: Stefan Roese <sr@denx.de> Cc: Albert ARIBAUD <albert-u-boot@aribaud.net> Cc: Vagrant Cascadian <vagrant@debian.org> Cc: Chris Packham <judge.packham@gmail.com> Cc: Tom Rini <trini@konsulko.com>
2019-04-25 09:53:18 +00:00
- BUILDMAN="kirkwood"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "buildman mvebu"
env:
travis-ci: Build mvebu boards (arm & aarch64) in separate job Its easier to watch the output of the build process when the platforms specific boards are grouped in a separate job. This patch adds a job for all mvebu boards (arm and aarch64). Signed-off-by: Stefan Roese <sr@denx.de> Cc: Tom Rini <trini@konsulko.com> Reviewed-by: Tom Rini <trini@konsulko.com>
2016-12-01 12:52:08 +00:00
- BUILDMAN="mvebu"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "buildman m68k"
env:
.travis.yml: rework according to new travis-ci infra - install using addons.apt - remove MAKEALL - split mpc85xx boards - remove TEST_CONFIG_CMD, just info - fetch mips toolchain via buildman - remove --list-error-boards param - conditional script - use TOOLCHAIN instead of INSTALL_TOOLCHAIN - add aarch64 - enable notifications via email Signed-off-by: Roger Meier <r.meier@siemens.com> Cc: Wolfgang Denk <wd@denx.de> Cc: Heiko Schocher <hs@denx.de> Cc: Tom Rini <trini@ti.com> Cc: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Cc: Andreas Färber <afaerber@suse.de> Tested-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Acked-by: Heiko Schocher <hs@denx.de>
2016-01-25 19:22:41 +00:00
- BUILDMAN="m68k"
TOOLCHAIN="m68k"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "buildman microblaze"
env:
Travis-CI: Fix microblaze and xilinx jobs Given how we handle the ARM toolchain we can't easily combine these two jobs, so don't. Give xilinx/ARM a separate build. Signed-off-by: Tom Rini <trini@konsulko.com>
2017-10-07 19:54:18 +00:00
- BUILDMAN="microblaze"
travis-ci: Add more architectures We can now build for microblaze, sh4 and xtensa. Signed-off-by: Tom Rini <trini@konsulko.com> Acked-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Heiko Schocher <hs@denx.de>
2016-10-20 15:23:15 +00:00
TOOLCHAIN="microblaze"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "buildman mips"
env:
.travis.yml: rework according to new travis-ci infra - install using addons.apt - remove MAKEALL - split mpc85xx boards - remove TEST_CONFIG_CMD, just info - fetch mips toolchain via buildman - remove --list-error-boards param - conditional script - use TOOLCHAIN instead of INSTALL_TOOLCHAIN - add aarch64 - enable notifications via email Signed-off-by: Roger Meier <r.meier@siemens.com> Cc: Wolfgang Denk <wd@denx.de> Cc: Heiko Schocher <hs@denx.de> Cc: Tom Rini <trini@ti.com> Cc: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Cc: Andreas Färber <afaerber@suse.de> Tested-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Acked-by: Heiko Schocher <hs@denx.de>
2016-01-25 19:22:41 +00:00
- BUILDMAN="mips"
TOOLCHAIN="mips"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "buildman non-Freescale PowerPC"
env:
- BUILDMAN="powerpc -x freescale"
buildman: support newer gcc versions from kernel.org Add support for gcc versions 7.3.0, 6.4.0 and 4.9.4. Also use a regex for matching the tarball names. Some gcc versions use '-ARCH-' instead of '_ARCH-'. As part of this, we switch TravisCI to also using these toolchains for all platforms. Signed-off-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Signed-off-by: Tom Rini <trini@konsulko.com>
2018-05-10 11:15:53 +00:00
TOOLCHAIN="powerpc"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "buildman mpc85xx&freescale (excluding many)"
env:
.travis.yml: Further optimizations - Xilinx aarch64 is caught in the general xilinx arm job, exclude from the general aarch64 job. - Give the generic aarch64 job a better name - Re-sort the PowerPC jobs so that we can complete them a bit quicker. Signed-off-by: Tom Rini <trini@konsulko.com>
2018-05-10 11:15:54 +00:00
- BUILDMAN="mpc85xx&freescale -x t208xrdb -x t4qds -x t102* -x p1_p2_rdb_pc -x p1010rdb -x corenet_ds -x b4860qds -x bsc91*"
buildman: support newer gcc versions from kernel.org Add support for gcc versions 7.3.0, 6.4.0 and 4.9.4. Also use a regex for matching the tarball names. Some gcc versions use '-ARCH-' instead of '_ARCH-'. As part of this, we switch TravisCI to also using these toolchains for all platforms. Signed-off-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Signed-off-by: Tom Rini <trini@konsulko.com>
2018-05-10 11:15:53 +00:00
TOOLCHAIN="powerpc"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "buildman t208xrdb corenet_ds"
env:
.travis.yml: Further optimizations - Xilinx aarch64 is caught in the general xilinx arm job, exclude from the general aarch64 job. - Give the generic aarch64 job a better name - Re-sort the PowerPC jobs so that we can complete them a bit quicker. Signed-off-by: Tom Rini <trini@konsulko.com>
2018-05-10 11:15:54 +00:00
- BUILDMAN="t208xrdb corenet_ds"
buildman: support newer gcc versions from kernel.org Add support for gcc versions 7.3.0, 6.4.0 and 4.9.4. Also use a regex for matching the tarball names. Some gcc versions use '-ARCH-' instead of '_ARCH-'. As part of this, we switch TravisCI to also using these toolchains for all platforms. Signed-off-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Signed-off-by: Tom Rini <trini@konsulko.com>
2018-05-10 11:15:53 +00:00
TOOLCHAIN="powerpc"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "buildman Freescale PowerPC"
env:
.travis.yml: Further optimizations - Xilinx aarch64 is caught in the general xilinx arm job, exclude from the general aarch64 job. - Give the generic aarch64 job a better name - Re-sort the PowerPC jobs so that we can complete them a bit quicker. Signed-off-by: Tom Rini <trini@konsulko.com>
2018-05-10 11:15:54 +00:00
- BUILDMAN="t4qds b4860qds mpc83xx&freescale mpc86xx&freescale"
buildman: support newer gcc versions from kernel.org Add support for gcc versions 7.3.0, 6.4.0 and 4.9.4. Also use a regex for matching the tarball names. Some gcc versions use '-ARCH-' instead of '_ARCH-'. As part of this, we switch TravisCI to also using these toolchains for all platforms. Signed-off-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Signed-off-by: Tom Rini <trini@konsulko.com>
2018-05-10 11:15:53 +00:00
TOOLCHAIN="powerpc"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "buildman t102*"
env:
Travis-CI: Split 't208xrdb t4qds t102*'-job into separate jobs The 't208xrdb t4qds t102*' job is close to the time limit and sometimes fails, so this splits it into 3 separate jobs. Signed-off-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
2017-12-20 10:06:31 +00:00
- BUILDMAN="t102*"
buildman: support newer gcc versions from kernel.org Add support for gcc versions 7.3.0, 6.4.0 and 4.9.4. Also use a regex for matching the tarball names. Some gcc versions use '-ARCH-' instead of '_ARCH-'. As part of this, we switch TravisCI to also using these toolchains for all platforms. Signed-off-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Signed-off-by: Tom Rini <trini@konsulko.com>
2018-05-10 11:15:53 +00:00
TOOLCHAIN="powerpc"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "buildman p1_p2_rdb_pc"
env:
travis-ci: Split p1_p2_rdb_pc and p1010rdb into separate jobs On occasion the job that does these two build types will hit the time limit so split this in two. Signed-off-by: Tom Rini <trini@konsulko.com>
2017-01-21 22:58:08 +00:00
- BUILDMAN="p1_p2_rdb_pc"
buildman: support newer gcc versions from kernel.org Add support for gcc versions 7.3.0, 6.4.0 and 4.9.4. Also use a regex for matching the tarball names. Some gcc versions use '-ARCH-' instead of '_ARCH-'. As part of this, we switch TravisCI to also using these toolchains for all platforms. Signed-off-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Signed-off-by: Tom Rini <trini@konsulko.com>
2018-05-10 11:15:53 +00:00
TOOLCHAIN="powerpc"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "buildman p1010rdb bsc91"
env:
.travis.yml: Further optimizations - Xilinx aarch64 is caught in the general xilinx arm job, exclude from the general aarch64 job. - Give the generic aarch64 job a better name - Re-sort the PowerPC jobs so that we can complete them a bit quicker. Signed-off-by: Tom Rini <trini@konsulko.com>
2018-05-10 11:15:54 +00:00
- BUILDMAN="p1010rdb bsc91"
buildman: support newer gcc versions from kernel.org Add support for gcc versions 7.3.0, 6.4.0 and 4.9.4. Also use a regex for matching the tarball names. Some gcc versions use '-ARCH-' instead of '_ARCH-'. As part of this, we switch TravisCI to also using these toolchains for all platforms. Signed-off-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Signed-off-by: Tom Rini <trini@konsulko.com>
2018-05-10 11:15:53 +00:00
TOOLCHAIN="powerpc"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "buildman siemens"
env:
.travis.yml: rework according to new travis-ci infra - install using addons.apt - remove MAKEALL - split mpc85xx boards - remove TEST_CONFIG_CMD, just info - fetch mips toolchain via buildman - remove --list-error-boards param - conditional script - use TOOLCHAIN instead of INSTALL_TOOLCHAIN - add aarch64 - enable notifications via email Signed-off-by: Roger Meier <r.meier@siemens.com> Cc: Wolfgang Denk <wd@denx.de> Cc: Heiko Schocher <hs@denx.de> Cc: Tom Rini <trini@ti.com> Cc: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Cc: Andreas Färber <afaerber@suse.de> Tested-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Acked-by: Heiko Schocher <hs@denx.de>
2016-01-25 19:22:41 +00:00
- BUILDMAN="siemens"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "buildman tegra"
env:
- BUILDMAN="tegra -x toradex"
- name: "buildman am33xx (no siemens)"
env:
- BUILDMAN="am33xx -x siemens"
- name: "buildman omap"
env:
.travis.yml: Further optimizations - Xilinx aarch64 is caught in the general xilinx arm job, exclude from the general aarch64 job. - Give the generic aarch64 job a better name - Re-sort the PowerPC jobs so that we can complete them a bit quicker. Signed-off-by: Tom Rini <trini@konsulko.com>
2018-05-10 11:15:54 +00:00
- BUILDMAN="omap"
travis: move orangepi to vendor job move orangepi builds into a new job, and exclude orangepi builds from sunxi and rockchip jobs. Signed-off-by: Heiko Schocher <hs@denx.de> Reviewed-by: Tom Rini <trini@konsulko.com>
2019-11-21 05:50:12 +00:00
- name: "buildman orangepi"
env:
- BUILDMAN="orangepi"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "buildman uniphier"
env:
travis.yml: Add in uniphier as a job, modify aarch64 builds a bit - Add in system aarch64-linux-gnu toolchain - Now that all VMs will have aarch64 available, don't exclude them from other jobs but instead exclude them from the catch-all aarch64 build - Add JOB= to the Freescale/ARM build to be clear about what it does. - Add uniphier as a stand-alone job Signed-off-by: Tom Rini <trini@konsulko.com>
2016-10-29 21:11:17 +00:00
- BUILDMAN="uniphier"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "buildman catch-all AArch64"
env:
Azure/Travis: Re-sync jobs and clarify exclusions We keep both of these jobs in sync as much as possible even when the primary motivation is to keep Travis from exceeding the build time limit there. With that in mind: - Use "rk" not "rockchip" to get all Rockchip SoC platforms in one job, rather than just all Rockchip vendor platforms. - The NXP LX216* SoCs have their own job, exclude them from the AArch64 generic job. - SoCFPGA SoCs have their own job, exclude them from the AArch64 generic job. Signed-off-by: Tom Rini <trini@konsulko.com>
2020-03-09 17:01:57 +00:00
- BUILDMAN="aarch64 -x bcm,k3,tegra,ls1,ls2,lx216,mvebu,uniphier,sunxi,samsung,socfpga,rk,versal,zynq"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "buildman rockchip"
env:
Azure/Travis: Re-sync jobs and clarify exclusions We keep both of these jobs in sync as much as possible even when the primary motivation is to keep Travis from exceeding the build time limit there. With that in mind: - Use "rk" not "rockchip" to get all Rockchip SoC platforms in one job, rather than just all Rockchip vendor platforms. - The NXP LX216* SoCs have their own job, exclude them from the AArch64 generic job. - SoCFPGA SoCs have their own job, exclude them from the AArch64 generic job. Signed-off-by: Tom Rini <trini@konsulko.com>
2020-03-09 17:01:57 +00:00
- BUILDMAN="rk -x orangepi"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "buildman sh"
env:
- BUILDMAN="sh -x arm"
buildman: support newer gcc versions from kernel.org Add support for gcc versions 7.3.0, 6.4.0 and 4.9.4. Also use a regex for matching the tarball names. Some gcc versions use '-ARCH-' instead of '_ARCH-'. As part of this, we switch TravisCI to also using these toolchains for all platforms. Signed-off-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Signed-off-by: Tom Rini <trini@konsulko.com>
2018-05-10 11:15:53 +00:00
TOOLCHAIN="sh"
travis: Split and rename xilinx ARM in to two jobs Split the ARMv7 and AArch64 platforms into separate jobs, to avoid them taking too long to build overall. Also rename them from "Xilinx" to "Zynq*" to reflect slightly better what is being built and to pull in a few more board matches. Reviewed-by: Michal Simek <michal.simek@xilinx.com> Signed-off-by: Tom Rini <trini@konsulko.com>
2019-10-14 22:12:59 +00:00
- name: "buildman Zynq* (ARMv7)"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
env:
travis: Split and rename xilinx ARM in to two jobs Split the ARMv7 and AArch64 platforms into separate jobs, to avoid them taking too long to build overall. Also rename them from "Xilinx" to "Zynq*" to reflect slightly better what is being built and to pull in a few more board matches. Reviewed-by: Michal Simek <michal.simek@xilinx.com> Signed-off-by: Tom Rini <trini@konsulko.com>
2019-10-14 22:12:59 +00:00
- BUILDMAN="zynq&armv7"
- name: "buildman ZynqMP and Versal"
env:
- BUILDMAN="versal|zynqmp&aarch64"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "buildman xtensa"
env:
travis-ci: Add more architectures We can now build for microblaze, sh4 and xtensa. Signed-off-by: Tom Rini <trini@konsulko.com> Acked-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Heiko Schocher <hs@denx.de>
2016-10-20 15:23:15 +00:00
- BUILDMAN="xtensa"
.travis.yml: download xtensa prebuilt toolchain xtensa toolchains are core-specific, so give full toolchain name and download corresponding prebuilt toolchain from the github release. Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
2018-02-07 23:30:01 +00:00
TOOLCHAIN="xtensa-dc233c-elf"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "buildman riscv"
env:
travis.yml: Support RISC-V Enable travis-ci support with a link having built. Signed-off-by: Chih-Mao Chen <cmchen@andestech.com> Signed-off-by: Rick Chen <rick@andestech.com> Signed-off-by: Rick Chen <rickchen36@gmail.com> Signed-off-by: Greentime Hu <green.hu@gmail.com>
2018-01-12 06:57:09 +00:00
- BUILDMAN="riscv"
TOOLCHAIN="riscv"
.travis.yml: Support nds32 prebuilt toolchain Download nds32 prebuild toolchain from github which is base on gcc 8.0.1 version for regression. Signed-off-by: Rick Chen <rick@andestech.com> Cc: Greentime Hu <greentime@andestech.com>
2019-01-14 05:36:15 +00:00
- name: "buildman nds32"
env:
- BUILDMAN="nds32"
TOOLCHAIN="nds32"
.travis.yml: build u-boot on travis-ci Goal: - building all variants of U-Boot with multiple configurations - code quality checks and metrics - https://travis-ci.org/u-boot/u-boot/builds
2014-11-19 14:26:18 +00:00
# QA jobs for code analytics
# static code analysis with cppcheck (we can add --enable=all later)
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "cppcheck"
travis-ci: set env vars to name jobs Travis CI names sub-jobs after the first environment variable that is set for a script. This doesn't produce meaningful results for any of the non- buildman jobs. Add a dummy variable to give the jobs meaningful names. Signed-off-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Tom Rini <trini@konsulko.com>
2016-10-24 22:41:48 +00:00
script:
travis/gitlab/azure: Run cppcheck in parallel This takes ages to run single-threaded. Adjust it to use all available processors. Signed-off-by: Simon Glass <sjg@chromium.org>
2020-04-05 20:35:43 +00:00
- cppcheck -j$(nproc) --force --quiet --inline-suppr .
travis: build HTML docs Several patches delivered incorrect restructured text as documentation. We should be able to discover this in Travis CI. Provide a build step for 'make htmldocs'. Add required package graphviz. Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
2020-02-21 17:24:00 +00:00
# build HTML documentation
- name: "htmldocs"
script:
- make htmldocs
.travis.yml: build u-boot on travis-ci Goal: - building all variants of U-Boot with multiple configurations - code quality checks and metrics - https://travis-ci.org/u-boot/u-boot/builds
2014-11-19 14:26:18 +00:00
# search for TODO within source tree
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "grep TODO"
travis-ci: set env vars to name jobs Travis CI names sub-jobs after the first environment variable that is set for a script. This doesn't produce meaningful results for any of the non- buildman jobs. Add a dummy variable to give the jobs meaningful names. Signed-off-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Tom Rini <trini@konsulko.com>
2016-10-24 22:41:48 +00:00
script:
travis-ci: Drop 'TEST_CMD' We don't need to use TEST_CMD in order to run tests. We need a BUILDMAN and TOOLCHAIN variable to avoid having to duplicate logic or write some wrapper function. But this makes the tests harder as we add more complex examples. Signed-off-by: Tom Rini <trini@konsulko.com> Acked-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Heiko Schocher <hs@denx.de>
2016-10-20 15:24:52 +00:00
- grep -r TODO .
.travis.yml: build u-boot on travis-ci Goal: - building all variants of U-Boot with multiple configurations - code quality checks and metrics - https://travis-ci.org/u-boot/u-boot/builds
2014-11-19 14:26:18 +00:00
# search for FIXME within source tree
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "grep FIXME HACK"
travis-ci: set env vars to name jobs Travis CI names sub-jobs after the first environment variable that is set for a script. This doesn't produce meaningful results for any of the non- buildman jobs. Add a dummy variable to give the jobs meaningful names. Signed-off-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Tom Rini <trini@konsulko.com>
2016-10-24 22:41:48 +00:00
script:
travis-ci: Drop 'TEST_CMD' We don't need to use TEST_CMD in order to run tests. We need a BUILDMAN and TOOLCHAIN variable to avoid having to duplicate logic or write some wrapper function. But this makes the tests harder as we add more complex examples. Signed-off-by: Tom Rini <trini@konsulko.com> Acked-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Heiko Schocher <hs@denx.de>
2016-10-20 15:24:52 +00:00
- grep -r FIXME .
.travis.yml: build u-boot on travis-ci Goal: - building all variants of U-Boot with multiple configurations - code quality checks and metrics - https://travis-ci.org/u-boot/u-boot/builds
2014-11-19 14:26:18 +00:00
# search for HACK within source tree and ignore HACKKIT board
script:
- grep -r HACK . | grep -v HACKKIT
# some statistics about the code base
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "sloccount"
travis-ci: set env vars to name jobs Travis CI names sub-jobs after the first environment variable that is set for a script. This doesn't produce meaningful results for any of the non- buildman jobs. Add a dummy variable to give the jobs meaningful names. Signed-off-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Tom Rini <trini@konsulko.com>
2016-10-24 22:41:48 +00:00
script:
travis-ci: Drop 'TEST_CMD' We don't need to use TEST_CMD in order to run tests. We need a BUILDMAN and TOOLCHAIN variable to avoid having to duplicate logic or write some wrapper function. But this makes the tests harder as we add more complex examples. Signed-off-by: Tom Rini <trini@konsulko.com> Acked-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Heiko Schocher <hs@denx.de>
2016-10-20 15:24:52 +00:00
- sloccount .
travis: Add check for configs without MAINTAINERS entries The genboardscfg.py script will emit a WARNING message if we have new defconfig files that are not listed in a MAINTAINERS file. Make new cases of this a failure we catch in Travis-CI. Signed-off-by: Tom Rini <trini@konsulko.com>
2018-12-06 21:39:43 +00:00
# ensure all configs have MAINTAINERS entries
- name: "Check for configs without MAINTAINERS entry"
script:
- if [ `./tools/genboardscfg.py -f 2>&1 | wc -l` -ne 0 ]; then exit 1; fi
tools: add a generic config for native tools building The motivation for this is to allow distributions to distribute all possible tools in a generic way, avoiding the need of specific tools building for each machine. Especially on OpenEmbedded / Yocto Project ecosystem, it is very common each BSP to end providing their specific tools when they need to generate images for some SoC (e.g MX23 / MX28 in meta-freescale case). Using this, we can package the tools doing: $: make tools-only_defconfig $: make tools-only Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> [trini: Add MAINTAINERS entry for myself, add to .travis.yml, make U-Boot itself buildable to not trip up other frameworks] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-12-08 00:00:41 +00:00
# Ensure host tools build
- name: "Build tools-only"
script:
- make tools-only_config tools-only -j$(nproc)
ci: add envtools support This commit add envtools suppport to CI to verify if there is no build issues. Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io> Acked-by: Heiko Schocher <hs@denx.de> Reviewed-by: Simon Glass <sjg@chromium.org>
2019-08-26 11:06:18 +00:00
# Ensure env tools build
- name: "Build envtools"
script:
- make tools-only_config envtools -j$(nproc)
travis-ci: compile with buildman when running test/py Use buildman to compile any U-Boot binary tested by test/py. This re-uses all the work done elsewhere to make buildman work within Travis-CI, in particular related to toolchain downloading and buildman config file creation. Signed-off-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Heiko Schocher <hs@denx.de>
2016-10-26 17:05:36 +00:00
Nokia RX-51: Add automated test for running RX-51 build in qemu This patch contains test/nokia_rx51_test.sh script which automatically download and compile all needed tools in local temporary directory to generate a simple MTD images for booting Maemo kernel image by U-Boot from RAM, eMMC and OneNAND. MTD images are then run in virtual n900 machine provided by qemu-linaro project. This script does not need any special privileges, so it can be run as non-root nobody user. It can be used to check that U-Boot for Nokia N900 is not broken and can be successfully booted in emulator. Script is registered to .azure-pipelines.yml, .gitlab-ci.yml and .travis.yml so it would be automatically run on those CI services. Signed-off-by: Pali Rohár <pali@kernel.org>
2020-05-17 12:38:22 +00:00
- name: "Run tests for Nokia RX-51 (aka N900)"
script:
- export PATH=~/.buildman-toolchains/gcc-9.2.0-nolibc/arm-linux-gnueabi/bin/:$PATH
- test/nokia_rx51_test.sh
Enable test/py for sandbox in Travis CI This provides runtime test coverage in Travis, in addition to the existing build coverage. Signed-off-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Roger Meier <r.meier@siemens.com> Reviewed-by: Heiko Schocher <hs@denx.de> Acked-by: Simon Glass <sjg@chromium.org>
2016-02-09 01:23:35 +00:00
# test/py
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "test/py sandbox"
env:
travis-ci: compile with buildman when running test/py Use buildman to compile any U-Boot binary tested by test/py. This re-uses all the work done elsewhere to make buildman work within Travis-CI, in particular related to toolchain downloading and buildman config file creation. Signed-off-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Heiko Schocher <hs@denx.de>
2016-10-26 17:05:36 +00:00
- TEST_PY_BD="sandbox"
travis: Switch to i386 version toolchain for x86 Currently this uses x86_64 version toolchain for x86 build in travis-ci. Change it to i386 version to avoid updating the buildman toolchain path every time when the toolchain version number is changed, eg: from 7.3.0 to 8.1.0. Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
2018-10-08 23:53:54 +00:00
TOOLCHAIN="i386"
travis: Add sandbox/clang-7 support To make testing with clang support easier, add sandbox/clang-7 combination to our testing matrix. To facilitate this, switch to using the "sources" method that the travis.yml file supports to list additional repositories and add the official one for llvm-7. Due to buildman not supporting using clang at this time add logic to manually build a single sandbox configuration in the expected output directory so that we can still invoke all of our tests. Cc: Simon Glass <sjg@chromium.org> Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org>
2018-10-07 18:20:30 +00:00
- name: "test/py sandbox with clang"
env:
- TEST_PY_BD="sandbox"
travis: Switch over to using LLVM-10 At this point LLVM-7 is rather old. Switch over to LLVM-10 to enable some amount of CI coverage with newer compilers. Signed-off-by: Tom Rini <trini@konsulko.com>
2020-02-12 22:14:57 +00:00
OVERRIDE="-O clang-10"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "test/py sandbox_spl"
env:
travis-ci: Emulate 'make tests' The 'tests' target will run sandbox, sandbox_spl and sandbox_flattree in test.py and in the case of sandbox_spl ensure that we just run the specific tests for that build. Update our matrix to perform similar test.py runs. Signed-off-by: Tom Rini <trini@konsulko.com>
2017-08-07 19:24:50 +00:00
- TEST_PY_BD="sandbox_spl"
travis/gitlab/azure: Enable test_handoff Ensure that this SPL test runs on gitlab. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Tom Rini <trini@konsulko.com>
2020-03-18 15:42:58 +00:00
TEST_PY_TEST_SPEC="test_ofplatdata or test_handoff"
travis: Switch to i386 version toolchain for x86 Currently this uses x86_64 version toolchain for x86 build in travis-ci. Change it to i386 version to avoid updating the buildman toolchain path every time when the toolchain version number is changed, eg: from 7.3.0 to 8.1.0. Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
2018-10-08 23:53:54 +00:00
TOOLCHAIN="i386"
travis.yml: Run tests for tools Run tests for the Python tools used by U-Boot. Signed-off-by: Simon Glass <sjg@chromium.org>
2017-11-27 03:26:00 +00:00
TEST_PY_TOOLS="yes"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "test/py sandbox_flattree"
env:
travis-ci: Emulate 'make tests' The 'tests' target will run sandbox, sandbox_spl and sandbox_flattree in test.py and in the case of sandbox_spl ensure that we just run the specific tests for that build. Update our matrix to perform similar test.py runs. Signed-off-by: Tom Rini <trini@konsulko.com>
2017-08-07 19:24:50 +00:00
- TEST_PY_BD="sandbox_flattree"
travis: Switch to i386 version toolchain for x86 Currently this uses x86_64 version toolchain for x86 build in travis-ci. Change it to i386 version to avoid updating the buildman toolchain path every time when the toolchain version number is changed, eg: from 7.3.0 to 8.1.0. Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
2018-10-08 23:53:54 +00:00
TOOLCHAIN="i386"
travis: Add ASPEED ast2500 to qemu tests Signed-off-by: Joel Stanley <joel@jms.id.au>
2019-07-04 01:35:17 +00:00
- name: "test/py evb-ast2500"
env:
- TEST_PY_BD="evb-ast2500"
TEST_PY_ID="--id qemu"
QEMU_TARGET="arm-softmmu"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "test/py vexpress_ca15_tc2"
env:
travis-ci: compile with buildman when running test/py Use buildman to compile any U-Boot binary tested by test/py. This re-uses all the work done elsewhere to make buildman work within Travis-CI, in particular related to toolchain downloading and buildman config file creation. Signed-off-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Heiko Schocher <hs@denx.de>
2016-10-26 17:05:36 +00:00
- TEST_PY_BD="vexpress_ca15_tc2"
TEST_PY_ID="--id qemu"
travis-ci: Switch to building QEMU First, there are a number of features in newer QEMU that will allow us to test a wider range of platforms, so we want to use at least v2.8.0. Second, making use of a PPA for QEMU fails from time to time. So we change to checking out and building a copy of QEMU when we know that we are going to use test.py and need QEMU to be installed. This adds around 4 minutes per test.py job that we run. Signed-off-by: Tom Rini <trini@konsulko.com>
2016-12-07 16:20:40 +00:00
QEMU_TARGET="arm-softmmu"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "test/py vexpress_ca9x4"
env:
travis-ci: compile with buildman when running test/py Use buildman to compile any U-Boot binary tested by test/py. This re-uses all the work done elsewhere to make buildman work within Travis-CI, in particular related to toolchain downloading and buildman config file creation. Signed-off-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Heiko Schocher <hs@denx.de>
2016-10-26 17:05:36 +00:00
- TEST_PY_BD="vexpress_ca9x4"
TEST_PY_ID="--id qemu"
travis-ci: Switch to building QEMU First, there are a number of features in newer QEMU that will allow us to test a wider range of platforms, so we want to use at least v2.8.0. Second, making use of a PPA for QEMU fails from time to time. So we change to checking out and building a copy of QEMU when we know that we are going to use test.py and need QEMU to be installed. This adds around 4 minutes per test.py job that we run. Signed-off-by: Tom Rini <trini@konsulko.com>
2016-12-07 16:20:40 +00:00
QEMU_TARGET="arm-softmmu"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "test/py integratorcp_cm926ejs"
env:
travis-ci: compile with buildman when running test/py Use buildman to compile any U-Boot binary tested by test/py. This re-uses all the work done elsewhere to make buildman work within Travis-CI, in particular related to toolchain downloading and buildman config file creation. Signed-off-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Heiko Schocher <hs@denx.de>
2016-10-26 17:05:36 +00:00
- TEST_PY_BD="integratorcp_cm926ejs"
Travis: Remove sleep test from integratorcp_cm926ejs-qemu test Most of the time when running the sleep test in Travis for the integratorcp_cm926ejs target I get errors like this: E assert 2.999901056289673 >= 3 The deviation is tiny, but fails the overall build result. Since the sleep test is not terribly important as gate keeper for travis tests, let's just exclude it for this board. Signed-off-by: Alexander Graf <agraf@suse.de> Reviewed-by: Tom Rini <trini@konsulko.com>
2016-11-17 17:31:07 +00:00
TEST_PY_TEST_SPEC="not sleep"
travis-ci: compile with buildman when running test/py Use buildman to compile any U-Boot binary tested by test/py. This re-uses all the work done elsewhere to make buildman work within Travis-CI, in particular related to toolchain downloading and buildman config file creation. Signed-off-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Heiko Schocher <hs@denx.de>
2016-10-26 17:05:36 +00:00
TEST_PY_ID="--id qemu"
travis-ci: Switch to building QEMU First, there are a number of features in newer QEMU that will allow us to test a wider range of platforms, so we want to use at least v2.8.0. Second, making use of a PPA for QEMU fails from time to time. So we change to checking out and building a copy of QEMU when we know that we are going to use test.py and need QEMU to be installed. This adds around 4 minutes per test.py job that we run. Signed-off-by: Tom Rini <trini@konsulko.com>
2016-12-07 16:20:40 +00:00
QEMU_TARGET="arm-softmmu"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "test/py qemu_arm"
env:
travis.yml: Add job for running test.py in qemu_arm Note that this commit requires https://github.com/swarren/uboot-test-hooks/pull/14 to go in first. Signed-off-by: Tuomas Tynkkynen <tuomas.tynkkynen@iki.fi>
2017-09-19 20:18:08 +00:00
- TEST_PY_BD="qemu_arm"
TEST_PY_TEST_SPEC="not sleep"
QEMU_TARGET="arm-softmmu"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "test/py qemu_arm64"
env:
Travis-CI: Add job for running test.py on qemu_arm64 The corresponding changes in the uboot-test-hooks repo are: https://github.com/swarren/uboot-test-hooks/pull/15 Signed-off-by: Tuomas Tynkkynen <tuomas.tynkkynen@iki.fi> Reviewed-by: Tom Rini <trini@konsulko.com>
2018-01-11 14:11:26 +00:00
- TEST_PY_BD="qemu_arm64"
TEST_PY_TEST_SPEC="not sleep"
QEMU_TARGET="aarch64-softmmu"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "test/py qemu_mips"
env:
travis-ci: compile with buildman when running test/py Use buildman to compile any U-Boot binary tested by test/py. This re-uses all the work done elsewhere to make buildman work within Travis-CI, in particular related to toolchain downloading and buildman config file creation. Signed-off-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Heiko Schocher <hs@denx.de>
2016-10-26 17:05:36 +00:00
- TEST_PY_BD="qemu_mips"
TEST_PY_TEST_SPEC="not sleep"
travis-ci: Switch to building QEMU First, there are a number of features in newer QEMU that will allow us to test a wider range of platforms, so we want to use at least v2.8.0. Second, making use of a PPA for QEMU fails from time to time. So we change to checking out and building a copy of QEMU when we know that we are going to use test.py and need QEMU to be installed. This adds around 4 minutes per test.py job that we run. Signed-off-by: Tom Rini <trini@konsulko.com>
2016-12-07 16:20:40 +00:00
QEMU_TARGET="mips-softmmu"
travis-ci: compile with buildman when running test/py Use buildman to compile any U-Boot binary tested by test/py. This re-uses all the work done elsewhere to make buildman work within Travis-CI, in particular related to toolchain downloading and buildman config file creation. Signed-off-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Heiko Schocher <hs@denx.de>
2016-10-26 17:05:36 +00:00
TOOLCHAIN="mips"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "test/py qemu_mipsel"
env:
travis-ci: compile with buildman when running test/py Use buildman to compile any U-Boot binary tested by test/py. This re-uses all the work done elsewhere to make buildman work within Travis-CI, in particular related to toolchain downloading and buildman config file creation. Signed-off-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Heiko Schocher <hs@denx.de>
2016-10-26 17:05:36 +00:00
- TEST_PY_BD="qemu_mipsel"
TEST_PY_TEST_SPEC="not sleep"
travis-ci: Switch to building QEMU First, there are a number of features in newer QEMU that will allow us to test a wider range of platforms, so we want to use at least v2.8.0. Second, making use of a PPA for QEMU fails from time to time. So we change to checking out and building a copy of QEMU when we know that we are going to use test.py and need QEMU to be installed. This adds around 4 minutes per test.py job that we run. Signed-off-by: Tom Rini <trini@konsulko.com>
2016-12-07 16:20:40 +00:00
QEMU_TARGET="mipsel-softmmu"
travis-ci: compile with buildman when running test/py Use buildman to compile any U-Boot binary tested by test/py. This re-uses all the work done elsewhere to make buildman work within Travis-CI, in particular related to toolchain downloading and buildman config file creation. Signed-off-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Heiko Schocher <hs@denx.de>
2016-10-26 17:05:36 +00:00
TOOLCHAIN="mips"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "test/py qemu_mips64"
env:
travis-ci: compile with buildman when running test/py Use buildman to compile any U-Boot binary tested by test/py. This re-uses all the work done elsewhere to make buildman work within Travis-CI, in particular related to toolchain downloading and buildman config file creation. Signed-off-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Heiko Schocher <hs@denx.de>
2016-10-26 17:05:36 +00:00
- TEST_PY_BD="qemu_mips64"
TEST_PY_TEST_SPEC="not sleep"
travis-ci: Switch to building QEMU First, there are a number of features in newer QEMU that will allow us to test a wider range of platforms, so we want to use at least v2.8.0. Second, making use of a PPA for QEMU fails from time to time. So we change to checking out and building a copy of QEMU when we know that we are going to use test.py and need QEMU to be installed. This adds around 4 minutes per test.py job that we run. Signed-off-by: Tom Rini <trini@konsulko.com>
2016-12-07 16:20:40 +00:00
QEMU_TARGET="mips64-softmmu"
travis-ci: compile with buildman when running test/py Use buildman to compile any U-Boot binary tested by test/py. This re-uses all the work done elsewhere to make buildman work within Travis-CI, in particular related to toolchain downloading and buildman config file creation. Signed-off-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Heiko Schocher <hs@denx.de>
2016-10-26 17:05:36 +00:00
TOOLCHAIN="mips"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "test/py qemu_mips64el"
env:
travis-ci: compile with buildman when running test/py Use buildman to compile any U-Boot binary tested by test/py. This re-uses all the work done elsewhere to make buildman work within Travis-CI, in particular related to toolchain downloading and buildman config file creation. Signed-off-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Heiko Schocher <hs@denx.de>
2016-10-26 17:05:36 +00:00
- TEST_PY_BD="qemu_mips64el"
TEST_PY_TEST_SPEC="not sleep"
travis-ci: Switch to building QEMU First, there are a number of features in newer QEMU that will allow us to test a wider range of platforms, so we want to use at least v2.8.0. Second, making use of a PPA for QEMU fails from time to time. So we change to checking out and building a copy of QEMU when we know that we are going to use test.py and need QEMU to be installed. This adds around 4 minutes per test.py job that we run. Signed-off-by: Tom Rini <trini@konsulko.com>
2016-12-07 16:20:40 +00:00
QEMU_TARGET="mips64el-softmmu"
travis-ci: compile with buildman when running test/py Use buildman to compile any U-Boot binary tested by test/py. This re-uses all the work done elsewhere to make buildman work within Travis-CI, in particular related to toolchain downloading and buildman config file creation. Signed-off-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Heiko Schocher <hs@denx.de>
2016-10-26 17:05:36 +00:00
TOOLCHAIN="mips"
.travis.yml: add Qemu tests for MIPS Malta board Add Qemu tests for the MIPS Malta machine as a replacement for the deprecated generic MIPS machine. Signed-off-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
2020-06-06 20:21:47 +00:00
- name: "test/py qemu-malta"
env:
- TEST_PY_BD="malta"
TEST_PY_TEST_SPEC="not sleep and not efi"
TEST_PY_ID="--id qemu"
QEMU_TARGET="mips-softmmu"
TOOLCHAIN="mips"
- name: "test/py qemu-maltael"
env:
- TEST_PY_BD="maltael"
TEST_PY_TEST_SPEC="not sleep and not efi"
TEST_PY_ID="--id qemu"
QEMU_TARGET="mipsel-softmmu"
TOOLCHAIN="mips"
- name: "test/py qemu-malta64"
env:
- TEST_PY_BD="malta64"
TEST_PY_TEST_SPEC="not sleep and not efi"
TEST_PY_ID="--id qemu"
QEMU_TARGET="mips64-softmmu"
TOOLCHAIN="mips"
- name: "test/py qemu-malta64el"
env:
- TEST_PY_BD="malta64el"
TEST_PY_TEST_SPEC="not sleep and not efi"
TEST_PY_ID="--id qemu"
QEMU_TARGET="mips64el-softmmu"
TOOLCHAIN="mips"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "test/py qemu-ppce500"
env:
travis-ci: compile with buildman when running test/py Use buildman to compile any U-Boot binary tested by test/py. This re-uses all the work done elsewhere to make buildman work within Travis-CI, in particular related to toolchain downloading and buildman config file creation. Signed-off-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Heiko Schocher <hs@denx.de>
2016-10-26 17:05:36 +00:00
- TEST_PY_BD="qemu-ppce500"
TEST_PY_TEST_SPEC="not sleep"
travis-ci: Switch to building QEMU First, there are a number of features in newer QEMU that will allow us to test a wider range of platforms, so we want to use at least v2.8.0. Second, making use of a PPA for QEMU fails from time to time. So we change to checking out and building a copy of QEMU when we know that we are going to use test.py and need QEMU to be installed. This adds around 4 minutes per test.py job that we run. Signed-off-by: Tom Rini <trini@konsulko.com>
2016-12-07 16:20:40 +00:00
QEMU_TARGET="ppc-softmmu"
buildman: support newer gcc versions from kernel.org Add support for gcc versions 7.3.0, 6.4.0 and 4.9.4. Also use a regex for matching the tarball names. Some gcc versions use '-ARCH-' instead of '_ARCH-'. As part of this, we switch TravisCI to also using these toolchains for all platforms. Signed-off-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Signed-off-by: Tom Rini <trini@konsulko.com>
2018-05-10 11:15:53 +00:00
TOOLCHAIN="powerpc"
azure/gitlab/travis: Add qemu-riscv32 testing This adds the qemu-riscv32_defconfig test configuration. Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
2020-03-28 14:25:27 +00:00
- name: "test/py qemu-riscv32"
env:
- TEST_PY_BD="qemu-riscv32"
TEST_PY_TEST_SPEC="not sleep"
QEMU_TARGET="riscv32-softmmu"
TOOLCHAIN="riscv"
travis.yml: run Python tests on qemu-riscv64_defconfig Run the Python tests on the RISC-V architecture too. https://github.com/swarren/uboot-test-hooks has already been updated. Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
2019-07-18 04:33:58 +00:00
- name: "test/py qemu-riscv64"
env:
- TEST_PY_BD="qemu-riscv64"
TEST_PY_TEST_SPEC="not sleep"
QEMU_TARGET="riscv64-softmmu"
TOOLCHAIN="riscv"
azure/gitlab/travis: Add RISC-V SPL testing This adds QEMU RISC-V 32/64 SPL testing. Unlike QEMU RISC-V 32/64, we test SPL running in M-mode and U-Boot proper running in S-mode, with a 4-core SMP configuration. Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
2020-03-28 14:25:29 +00:00
- name: "test/py qemu-riscv32_spl"
env:
- TEST_PY_BD="qemu-riscv32_spl"
TEST_PY_TEST_SPEC="not sleep"
QEMU_TARGET="riscv32-softmmu"
TOOLCHAIN="riscv"
- name: "test/py qemu-riscv64_spl"
env:
- TEST_PY_BD="qemu-riscv64_spl"
TEST_PY_TEST_SPEC="not sleep"
QEMU_TARGET="riscv64-softmmu"
TOOLCHAIN="riscv"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "test/py qemu-x86"
env:
travis-ci: compile with buildman when running test/py Use buildman to compile any U-Boot binary tested by test/py. This re-uses all the work done elsewhere to make buildman work within Travis-CI, in particular related to toolchain downloading and buildman config file creation. Signed-off-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Heiko Schocher <hs@denx.de>
2016-10-26 17:05:36 +00:00
- TEST_PY_BD="qemu-x86"
TEST_PY_TEST_SPEC="not sleep"
travis-ci: Switch to building QEMU First, there are a number of features in newer QEMU that will allow us to test a wider range of platforms, so we want to use at least v2.8.0. Second, making use of a PPA for QEMU fails from time to time. So we change to checking out and building a copy of QEMU when we know that we are going to use test.py and need QEMU to be installed. This adds around 4 minutes per test.py job that we run. Signed-off-by: Tom Rini <trini@konsulko.com>
2016-12-07 16:20:40 +00:00
QEMU_TARGET="i386-softmmu"
travis: Switch to i386 version toolchain for x86 Currently this uses x86_64 version toolchain for x86 build in travis-ci. Change it to i386 version to avoid updating the buildman toolchain path every time when the toolchain version number is changed, eg: from 7.3.0 to 8.1.0. Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
2018-10-08 23:53:54 +00:00
TOOLCHAIN="i386"
travis-ci: compile with buildman when running test/py Use buildman to compile any U-Boot binary tested by test/py. This re-uses all the work done elsewhere to make buildman work within Travis-CI, in particular related to toolchain downloading and buildman config file creation. Signed-off-by: Stephen Warren <swarren@nvidia.com> Reviewed-by: Heiko Schocher <hs@denx.de>
2016-10-26 17:05:36 +00:00
BUILD_ROM="yes"
travis: Add qemu-x86_64 target for test.py testing Add qemu-x86_64 to the list of targets we use for test.py runs. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
2018-10-14 03:52:14 +00:00
- name: "test/py qemu-x86_64"
env:
- TEST_PY_BD="qemu-x86_64"
TEST_PY_TEST_SPEC="not sleep"
QEMU_TARGET="x86_64-softmmu"
TOOLCHAIN="i386"
BUILD_ROM="yes"
ARM: zynq: Switch to single zynq configurations There are a lot of zynq configurations which can be merged together and use only one for all. The similar change has been done for ZynqMP by commit be1b6c32d940 ("arm64: zynqmp: Use zynqmp_virt platform") Build SPL with u-boot.img for zc706 like this. export DEVICE_TREE=zynq-zc706 && make xilinx_zynq_virt_defconfig && make -j8 u-boot.img is generic for all boards. Tested on Zybo, zc702, zc706, zc770-xm011-x16, cc108 and microzed. Signed-off-by: Michal Simek <michal.simek@xilinx.com>
2020-02-13 14:03:29 +00:00
- name: "test/py xilinx_zynq_virt"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
env:
ARM: zynq: Switch to single zynq configurations There are a lot of zynq configurations which can be merged together and use only one for all. The similar change has been done for ZynqMP by commit be1b6c32d940 ("arm64: zynqmp: Use zynqmp_virt platform") Build SPL with u-boot.img for zc706 like this. export DEVICE_TREE=zynq-zc706 && make xilinx_zynq_virt_defconfig && make -j8 u-boot.img is generic for all boards. Tested on Zybo, zc702, zc706, zc770-xm011-x16, cc108 and microzed. Signed-off-by: Michal Simek <michal.simek@xilinx.com>
2020-02-13 14:03:29 +00:00
- TEST_PY_BD="xilinx_zynq_virt"
travis-ci: Add zynq_zc702 target support It depends on qemu v2.8.0-rc3 which includes device loader property. Signed-off-by: Michal Simek <michal.simek@xilinx.com>
2016-12-14 08:47:23 +00:00
TEST_PY_TEST_SPEC="not sleep"
QEMU_TARGET="arm-softmmu"
TEST_PY_ID="--id qemu"
travis: Wire Xilinx Versal Virt platform Test Xilinx Versal Virt platform running on the v3.1.0 Qemu. Signed-off-by: Michal Simek <michal.simek@xilinx.com>
2018-12-20 07:40:25 +00:00
- name: "test/py xilinx_versal_virt"
env:
- TEST_PY_BD="xilinx_versal_virt"
TEST_PY_TEST_SPEC="not sleep"
QEMU_TARGET="aarch64-softmmu"
TEST_PY_ID="--id qemu"
travis: give every job a name Travis CI now supports giving jobs an explicit name. Do this for all jobs. This allows more direct control over jobs names than the previous automatic or implicit naming based on the environment variables or script text. Signed-off-by: Stephen Warren <swarren@nvidia.com> [trini: Update names for jobs added/changed since posting] Signed-off-by: Tom Rini <trini@konsulko.com>
2018-07-30 16:19:43 +00:00
- name: "test/py xtfpga"
env:
.travis.yml: test xtensa xtfpga board in QEMU This allows running tests on emulated KC705 board with DC233C xtensa core. It expects to find conf.xtfpga_qemu in the uboot-test-hooks. Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
2018-02-07 23:30:03 +00:00
- TEST_PY_BD="xtfpga"
TEST_PY_TEST_SPEC="not sleep"
QEMU_TARGET="xtensa-softmmu"
TEST_PY_ID="--id qemu"
TOOLCHAIN="xtensa-dc233c-elf"
.travis.yml: build u-boot on travis-ci Goal: - building all variants of U-Boot with multiple configurations - code quality checks and metrics - https://travis-ci.org/u-boot/u-boot/builds
2014-11-19 14:26:18 +00:00
# TODO make it perfect ;-r
Reference in a new issue Copy permalink