summaryrefslogtreecommitdiff
path: root/.azure-pipelines.yml
Commit message (Collapse)AuthorAgeFilesLines
* CI: treat documentation warnings as errorsHeinrich Schuchardt2023-05-041-1/+1
| | | | | | | | | | | We do not want to merge documentation that produces Sphinx warnings. scripts/kernel-doc uses environment variable KDOC_WERROR to determine if warnings should be treated as errors. Reported-by: Tom Rini <trini@konsulko.com> Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com> Reviewed-by: Simon Glass <sjg@chromium.org>
* CI: Add m68k targetMarek Vasut2023-04-151-0/+5
| | | | | | | | | | | | Add M5208EVBE board to CI. This does not use default config due to limitations of QEMU emulation, instead the timer is switched from DMA timer to PIT timer and RAMBAR accesses are inhibited. Local QEMU launch command is as follows: $ qemu-system-m68k -nographic -machine mcf5208evb -cpu m5208 -bios u-boot.bin Signed-off-by: Marek Vasut <marek.vasut+renesas@mailbox.org> Acked-by: Angelo Dureghello <angelo@kernel-space.org>
* CI: Move to clang-16Tom Rini2023-04-041-3/+3
| | | | | | | As this is now the stable release, move to using that now for our tests. Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org>
* CI: Ensure that vpl test is runSimon Glass2023-04-031-1/+1
| | | | | | | This is actually skipped at present due to the condition in the file. Fix this by running all vpl tests. Signed-off-by: Simon Glass <sjg@chromium.org>
* Azure CI: Be explicit about pytest cache directoryTom Rini2023-03-211-1/+1
| | | | | | | | | The default pytest cache directory is in a read-only directory in Azure, which results in a warning on the build page. Use the pytest command line option to set the cache dir to somewhere writable. Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org>
* Azure CI: Save pytest output automaticallyTom Rini2023-03-211-1/+2
| | | | | | | | Enable use of the python-azurepipelines package which provides automatic formatting and uploading of the pytest output. Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org>
* Dockerfile: Update to latest "Jammy" tagTom Rini2023-03-211-1/+1
| | | | | | Update to using the latest "Jammy" tag as our base. Signed-off-by: Tom Rini <trini@konsulko.com>
* CI: Add a check for building tools for PyPiSimon Glass2023-03-081-0/+10
| | | | | | Add a simple check that the PyPi packages can be built. Signed-off-by: Simon Glass <sjg@chromium.org>
* CI: Update test/nokia_rx51_test.sh to use prebuilt imagesPali Rohár2023-02-241-1/+8
| | | | | | | | | | Now that the Dockerfile creates images which have the binaries we require included, have CI make symlinks for them and update the existing script to support this. Signed-off-by: Tom Rini <trini@konsulko.com> Signed-off-by: Pali Rohár <pali@kernel.org> Reviewed-by: Simon Glass <sjg@chromium.org>
* CI: Add a check for pre-schema driver model tagsSimon Glass2023-02-141-0/+12
| | | | | | | These should not be used anymore. Add a check to ensure they don't creek back into U-Boot. Use bootph-... instead. Signed-off-by: Simon Glass <sjg@chromium.org>
* CI, Docker: Update to Jammy 2023016 tagTom Rini2023-02-111-1/+1
| | | | | | Move to the latest tag for "Jammy" and rebuild the containers. Signed-off-by: Tom Rini <trini@konsulko.com>
* trace: Add a testSimon Glass2023-02-111-0/+8
| | | | | | | | Add a test which runs sandbox, collects a trace and makes sure it can be processed by trace-cmd. This should ensure that this feature continues to work as U-Boot and trace-cmd evolve. Signed-off-by: Simon Glass <sjg@chromium.org>
* CI: Make check for new defined CONFIG symbols even more robustTom Rini2023-01-201-1/+2
| | | | | | | | | | | | | | | | | Now that all remaining in-tree cases where we define or undef a CONFIG symbol have been migrated to Kconfig or renamed to CFG we can make the CI check more robust. We will exclude the doc, tools and arch/arm/dts directories from this check as they are special cases. Further, we can exclude the scripts/kconfig/lkc.h and include/linux/kconfig.h files as the CONFIG values they define are special tooling cases and not real symbols. In the case of docs, the only places that currently fail this test are old documentation that should be rewritten so that we can remove this special case. Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org>
* doc: build infodocs target on Gitlab CI, AzureHeinrich Schuchardt2023-01-131-2/+3
| | | | | | | | Add infodocs target to CI testing. Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Tom Rini <trini@konsulko.com>
* CI/Docker: Update to jammy-20221130 tagTom Rini2023-01-111-1/+1
| | | | | | | | Update to the latest "jammy" tag. This requires us to list libc6-i386 as a required package to install (for nokia_rx51 tests) that was previously implicit. Signed-off-by: Tom Rini <trini@konsulko.com>
* Merge branch 'next'Tom Rini2023-01-091-31/+12
|\ | | | | | | Signed-off-by: Tom Rini <trini@konsulko.com>
| * CI: Replace unmigrated symbol test with non-Kconfig introduction testTom Rini2022-12-231-25/+6
| | | | | | | | | | | | | | | | | | | | | | | | Now that all symbols have been migrated to Kconfig, or are part of the CFG namespace we do not need a complex check for unmigrated CONFIG symbols. Any instance of #define (or #undef) or a CONFIG value is wrong, so cause CI to fail. This test is not as strict as possible yet as we have more symbols that were not previously caught to deal with. Signed-off-by: Tom Rini <trini@konsulko.com>
| * CI: Update to gcc-12.2Tom Rini2022-12-061-4/+4
| | | | | | | | | | | | | | - Update to gcc-12.2, and cherry-pick a fix in grub for risc-v Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * sandbox: Rework how SDL is enabled / disabledTom Rini2022-12-051-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | Given that we can use Kconfig logic directly to see if we have a program available on the host or not, change from passing NO_SDL to instead controlling CONFIG_SANDBOX_SDL in Kconfig directly. Introduce CONFIG_HOST_HAS_SDL as the way to test for sdl2-config and default CONFIG_SANDBOX_SDL on if we have that, or not. Cc: Simon Glass <sjg@chromium.org> Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org>
* | CI: Rework rockchip jobs in AzureTom Rini2022-12-291-2/+4
| | | | | | | | | | | | | | The rockchip job is getting close to the hard time limit in Azure for the free tier. Split this in to 32bit and 64bit board jobs. Signed-off-by: Tom Rini <trini@konsulko.com>
* | CI: Reduce aarch64 catchall job matchesTom Rini2022-12-221-4/+6
|/ | | | | | | | | The aarch64 catch-all job is getting close to the hard time limit in Azure for the free tier. Move i.MX9 boards to the i.MX8 job and move amlogic entirely to its own job. This brings us down from 85 boards to 51 boards and so should be safe for a while. Signed-off-by: Tom Rini <trini@konsulko.com>
* CI: Make more use of git safe.directoryTom Rini2022-11-241-0/+2
| | | | | | | | | | We have a number of jobs that will have git complain about needing to set safe.directory and this being untrue as a fatal error, but then complete. Set this flag correctly now as it should be used, and may prevent a future failure. Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org>
* buildman: Add --allow-missing flag to allow missing blobsTom Rini2022-11-221-1/+1
| | | | | | | | | | | | Add a new flag to buildman so that we will in turn pass BINMAN_ALLOW_MISSING=1 to 'make'. Make use of this flag in CI. Allow the settings file to control this. Cc: Rasmus Villemoes <rasmus.villemoes@prevas.dk> Cc: Simon Glass <sjg@chromium.org> Signed-off-by: Tom Rini <trini@konsulko.com> Signed-off-by: Simon Glass <sjg@chromium.org>
* CI: Update to jammy-20221003-17Oct2022 tagTom Rini2022-10-171-1/+1
| | | | | | | This includes python3-pyelftools so we can drop it from one of the tests directly. Signed-off-by: Tom Rini <trini@konsulko.com>
* docker: install riscv32 toolchainHeinrich Schuchardt2022-10-071-1/+1
| | | | | | | | | | | | | | | For building riscv32 targets we should use the riscv32 toolchain. Add it to the Docker image. Drop the riscv toolchain-alias as we do not need it in future. While in here, update to the latest "jammy" tag. Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com> Reviewed-by: Tom Rini <trini@konsulko.com> Reviewed-by: Rick Chen <rick@andestech.com> [trini: Update to latest jammy tag] Signed-off-by: Tom Rini <trini@konsulko.com>
* ci: Add a test for a non-LTO buildSimon Glass2022-09-021-0/+4
| | | | | | Check that sandbox builds and runs tests OK with LTO disabled. Signed-off-by: Simon Glass <sjg@chromium.org>
* CI: Move to Ubuntu 2022.04 "Jammy" for CI baseTom Rini2022-08-221-7/+7
| | | | | | | | | | | | | | | | - We now have a new enough sbsigntools in the distro, stop building. - Use the 20220801 tag for Jammy. - Move to pygit2 1.9.2 (current version) as the old one doesn't build on "Jammy". - Add the working directory to the list of safe directories for git. - Move to pytest 6.2.5 to address other issues. - This move exposed a number of minor issues in the existing scripts we used within CI to perform the jobs themselves. The most notable changes here involve using 'set +e / set -e' to enforce when we should or should not make non-zero buildman status be a fatal error. Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org>
* CI: Azure: Merge PowerPC jobs in to oneTom Rini2022-08-201-12/+2
| | | | | | | | At this point given the number of PowerPC platforms we have, a single job to build them all fits within the time limit we have in Azure. Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org>
* ppc: Remove corenet_ds boardsTom Rini2022-08-201-3/+1
| | | | | | | | | These boards have been orphaned for some time and are behind on various DM migrations. Remove them. Cc: Priyanka Jain <priyanka.jain@nxp.com> Cc: Peng Fan <peng.fan@nxp.com> Signed-off-by: Tom Rini <trini@konsulko.com>
* CI: Azure: Move to using macOS-12 imageTom Rini2022-08-121-1/+1
| | | | | | | As per https://github.com/actions/virtual-environments/issues/5583 the macOS-10.15 image is being deprecated. Move us up to macOS-12. Signed-off-by: Tom Rini <trini@konsulko.com>
* CI: Azure: Move to Ubuntu 22.04 imageTom Rini2022-08-121-1/+1
| | | | | | | | | | As per https://github.com/actions/runner-images/issues/6002 the Ubuntu 18.04 image is deprecated and will be removed by December 1, 2022. Move to the Ubuntu 22.04 image as our base for launching our containers from. Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org>
* gitlab/azure: Use buildman instead of genboardscfgSimon Glass2022-08-051-1/+1
| | | | | | | Use the equivalent buildman functionality to check maintainer info. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Tom Rini <trini@konsulko.com>
* CI: Add Aspeed AST2600Joel Stanley2022-07-061-0/+3
| | | | | | | | | The AST2600 has a Qemu model that allows testing. Create a SPI NOR image containing the combined SPL and u-boot FIT image. Reviewed-by: Chia-Wei Wang <chiawei_wang@aspeedtech.com> Reviewed-by: Cédric Le Goater <clg@kaod.org> Signed-off-by: Joel Stanley <joel@jms.id.au>
* CI: Azure: Build with ASAN enabledAndrew Scull2022-06-231-0/+6
| | | | | | | | In order to prevent build regressions with ASAN, add the builds to CI. The longer term objective will be to enabled test targets with ASAN enabled, but there are too many at the moment. Signed-off-by: Andrew Scull <ascull@google.com>
* CI: Azure: Rework how we update MSYS2Tom Rini2022-05-031-2/+3
| | | | | | | | | Based on reading https://www.msys2.org/docs/ci/ and "Other Systems" rework how we update MSYS2 to the current version. We run it once, to perform nothing other than being the first run, then we run pacman twice. Signed-off-by: Tom Rini <trini@konsulko.com>
* CI: Run VPL testsSimon Glass2022-05-021-0/+3
| | | | | | | Add tests for VPL into the mix. For now this just runs the help test and a few SPL ones. Signed-off-by: Simon Glass <sjg@chromium.org>
* nds32: Remove the architectureTom Rini2022-04-251-3/+3
| | | | | | | | | As removal of nds32 has been ack'd for the Linux kernel, remove support here as well. Cc: Rick Chen <rick@andestech.com> Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Rick Chen <rick@andestech.com>
* CI: Print out unmigrated symbols when failingTom Rini2022-04-151-2/+5
| | | | | | | | | To make addressing the problem of migrated symbols being present in board config header files, update the CI test to them print what symbols are causing it to fail. Also report all failures in the tree, rather than stopping at the first failing file. Signed-off-by: Tom Rini <trini@konsulko.com>
* CI: Update unmigrated symbol checkTom Rini2022-04-011-2/+4
| | | | | | | We need to check for config header files that #undef migrated symbols as well. Signed-off-by: Tom Rini <trini@konsulko.com>
* CI: Pin pylint version to 2.12.2Tom Rini2022-03-251-1/+1
| | | | | | | For consistency in runs, we need to always use the same pylint version. Pin to 2.12.2 as this is what we have been using so far. Signed-off-by: Tom Rini <trini@konsulko.com>
* CI: Fix unmigrated symbol testTom Rini2022-03-181-1/+1
| | | | | | | | | When calling comm to compare the CONFIG symbols a defconfig uses with the symbols that have been migrated, we need to suppress all output as the summary line will have everything we need. Failure to do this leads to the test blowing up, but in non-fatal ways. Signed-off-by: Tom Rini <trini@konsulko.com>
* CI, Docker: Update to latest focal tagTom Rini2022-03-151-1/+1
| | | | Signed-off-by: Tom Rini <trini@konsulko.com>
* Azure/GitLab CI: Add the pylint checkerSimon Glass2022-03-021-0/+22
| | | | | | | Add a check that new Python code does not regress the pylint score for any module. Signed-off-by: Simon Glass <sjg@chromium.org>
* tools: mkeficapsule: allow for specifying GUID explicitlyAKASHI Takahiro2022-02-111-2/+2
| | | | | | | | | | | | | | | | | | The existing options, "--fit" and "--raw," are only used to put a proper GUID in a capsule header, where GUID identifies a particular FMP (Firmware Management Protocol) driver which then would handle the firmware binary in a capsule. In fact, mkeficapsule does the exact same job in creating a capsule file whatever the firmware binary type is. To prepare for the future extension, the command syntax will be a bit modified to allow users to specify arbitrary GUID for their own FMP driver. OLD: [--fit <image> | --raw <image>] <capsule file> NEW: [--fit | --raw | --guid <guid-string>] <image> <capsule file> Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org> Reviewed-by: Simon Glass <sjg@chromium.org>
* tools: mkeficapsule: add firmware image signingAKASHI Takahiro2022-02-111-1/+1
| | | | | | | | | | | | | | | | | | | | With this enhancement, mkeficapsule will be able to sign a capsule file when it is created. A signature added will be used later in the verification at FMP's SetImage() call. To do that, we need specify additional command parameters: -monotonic-cout <count> : monotonic count -private-key <private key file> : private key file -certificate <certificate file> : certificate file Only when all of those parameters are given, a signature will be added to a capsule file. Users are expected to maintain and increment the monotonic count at every time of the update for each firmware image. Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org> Reviewed-by: Simon Glass <sjg@chromium.org> Acked-by: Ilias Apalodimas <ilias.apalodimas@linaro.org>
* CI: enforce packages upgrade for Msys2 on WindowsAKASHI Takahiro2022-02-111-0/+1
| | | | | | | | | | | | | | | | | | | We need to install libgnutls-devel package to build the host tool, mkeficapsule, and as of now, there seems to be a depencency conflict in the current msys2 installer; :: installing libp11-kit (0.24.1-1) breaks dependency \ 'libp11-kit=0.23.22' required by p11-kit To resolve this conflict, however, the initial "pacman -Syyuu" in 'tools_only_windows' job is not enough. Another "pacman -Su" will enforce all the out-of-date packages being upgraded. (Probably the first "-Syyuu" can be changed to "-Syu".) See the installation steps in https://www.msys2.org/ Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
* Dockfile, CI: Update to latest focal tag and buildTom Rini2022-02-031-1/+1
| | | | | | | - Latest focal tag - Add libgnutls to image Signed-off-by: Tom Rini <trini@konsulko.com>
* gitlab/azure: x86: Add a coreboot testSimon Glass2022-01-281-0/+10
| | | | | | | | | | | | | | | | | Coreboot supports U-Boot as a payload and this recently got a bit of a facelist. Add a test for this. For now this uses a binary build of coreboot (v4.15). Future work could potentially build it from source, but we need to figure out the toolchain problems first, since coreboot uses its own toolchain. It turns out that this is tricky, because coreboot fails to build with a vanilla gcc. This needs some changes to the hooks scripts as well. An example build is at https://source.denx.de/u-boot/custodians/u-boot-dm/-/jobs/359687 Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Tom Rini <trini@konsulko.com>
* CI, Dockerfile: Update to latest "focal" tagTom Rini2022-01-121-1/+1
| | | | | | | Bring us to the focal-20220105 tag and rebuild our images on top of this. Signed-off-by: Tom Rini <trini@konsulko.com>
* ci: azure: Update to use stagesTom Rini2022-01-121-1/+7
| | | | | | | | Follow what we do in GitLab CI where we break the jobs up in to stages such that if earlier and often quicker sanity tests fail we don't run everything else. Signed-off-by: Tom Rini <trini@konsulko.com>
View Lorry Controller Status