fb83fd3b84
The verbosity adds a lot of unnecessary output to the CI logs which end up getting truncated anyway. We can always extract information from the meson test logs on a failure and for the custom runners its generally easier to re-create failures anyway. Signed-off-by: Alex Bennée <alex.bennee@linaro.org> Reviewed-by: Thomas Huth <thuth@redhat.com> Message-Id: <20221221090411.1995037-3-alex.bennee@linaro.org>
26 lines
767 B
YAML
26 lines
767 B
YAML
# All ubuntu-22.04 jobs should run successfully in an environment
|
|
# setup by the scripts/ci/setup/qemu/build-environment.yml task
|
|
# "Install basic packages to build QEMU on Ubuntu 20.04"
|
|
|
|
ubuntu-22.04-aarch32-all:
|
|
needs: []
|
|
stage: build
|
|
tags:
|
|
- ubuntu_22.04
|
|
- aarch32
|
|
rules:
|
|
- if: '$CI_PROJECT_NAMESPACE == "qemu-project" && $CI_COMMIT_BRANCH =~ /^staging/'
|
|
when: manual
|
|
allow_failure: true
|
|
- if: "$AARCH32_RUNNER_AVAILABLE"
|
|
when: manual
|
|
allow_failure: true
|
|
script:
|
|
- mkdir build
|
|
- cd build
|
|
- ../configure --cross-prefix=arm-linux-gnueabihf-
|
|
|| { cat config.log meson-logs/meson-log.txt; exit 1; }
|
|
- make --output-sync -j`nproc --ignore=40`
|
|
- make --output-sync -j`nproc --ignore=40` check
|
|
|| { cat meson-logs/testlog.txt; exit 1; } ;
|