998f334722
When tests fail meson just displays a summary and tells you to look at the testlog.txt file for details. The native jobs on shared runners publish testlog.txt as an artifact. For the Cirrus jobs and custom runner jobs this is not currently possible. The best we can do is cat the log contents on failure, to give maintainers a fighting chance of diagnosing the problem. Reviewed-by: Thomas Huth <thuth@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> Message-Id: <20220722130431.2319019-3-berrange@redhat.com> Signed-off-by: Alex Bennée <alex.bennee@linaro.org> Message-Id: <20220725140520.515340-3-alex.bennee@linaro.org>
38 lines
1.1 KiB
YAML
38 lines
1.1 KiB
YAML
@CIRRUS_VM_INSTANCE_TYPE@:
|
|
@CIRRUS_VM_IMAGE_SELECTOR@: @CIRRUS_VM_IMAGE_NAME@
|
|
cpu: @CIRRUS_VM_CPUS@
|
|
memory: @CIRRUS_VM_RAM@
|
|
|
|
env:
|
|
CIRRUS_CLONE_DEPTH: 1
|
|
CI_REPOSITORY_URL: "@CI_REPOSITORY_URL@"
|
|
CI_COMMIT_REF_NAME: "@CI_COMMIT_REF_NAME@"
|
|
CI_COMMIT_SHA: "@CI_COMMIT_SHA@"
|
|
PATH: "@PATH@"
|
|
PKG_CONFIG_PATH: "@PKG_CONFIG_PATH@"
|
|
PYTHON: "@PYTHON@"
|
|
MAKE: "@MAKE@"
|
|
CONFIGURE_ARGS: "@CONFIGURE_ARGS@"
|
|
TEST_TARGETS: "@TEST_TARGETS@"
|
|
|
|
build_task:
|
|
install_script:
|
|
- @UPDATE_COMMAND@
|
|
- @INSTALL_COMMAND@ @PKGS@
|
|
- if test -n "@PYPI_PKGS@" ; then @PIP3@ install @PYPI_PKGS@ ; fi
|
|
clone_script:
|
|
- git clone --depth 100 "$CI_REPOSITORY_URL" .
|
|
- git fetch origin "$CI_COMMIT_REF_NAME"
|
|
- git reset --hard "$CI_COMMIT_SHA"
|
|
build_script:
|
|
- mkdir build
|
|
- cd build
|
|
- ../configure --enable-werror $CONFIGURE_ARGS
|
|
|| { cat config.log meson-logs/meson-log.txt; exit 1; }
|
|
- $MAKE -j$(sysctl -n hw.ncpu)
|
|
- for TARGET in $TEST_TARGETS ;
|
|
do
|
|
$MAKE -j$(sysctl -n hw.ncpu) $TARGET V=1
|
|
|| { cat meson-logs/testlog.txt; exit 1; } ;
|
|
done
|