luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-11-14 21:36:13 +01:00
Code Issues Packages Projects Releases Wiki Activity
deb495de42
glib/.gitlab-ci/test-msys2.sh

69 lines
1.7 KiB
Bash
Raw Normal View History

gitlab-ci: Add 32bit MinGW jobs using MSYS2 This builds glib using meson/ninja/ccache with mingw-w64 on a Windows machine. The CI scripts expect a gitlab runner to exist with the "win32" tag which uses the default "cmd" shell by default. Before running the tests pacman is invoked to update the system (potentially including bash etc, thus the extra step) Then a login shell is started with CHERE_INVOKING to not change the cwd and finally the test script is executed. https://bugzilla.gnome.org/show_bug.cgi?id=793729
2018-02-22 19:37:16 +01:00
#!/bin/bash
ci/test-msys2: use $MINGW_PACKAGE_PREFIX
2022-10-29 02:29:38 +02:00
set -ex
gitlab-ci: Add 32bit MinGW jobs using MSYS2 This builds glib using meson/ninja/ccache with mingw-w64 on a Windows machine. The CI scripts expect a gitlab runner to exist with the "win32" tag which uses the default "cmd" shell by default. Before running the tests pacman is invoked to update the system (potentially including bash etc, thus the extra step) Then a login shell is started with CHERE_INVOKING to not change the cwd and finally the test script is executed. https://bugzilla.gnome.org/show_bug.cgi?id=793729
2018-02-22 19:37:16 +01:00
export PATH="/c/msys64/$MSYSTEM/bin:$PATH"
pacman --noconfirm -Suy
pacman --noconfirm -S --needed \
base-devel \
CI: Re-enable code coverage reporting for MSYS2 builds It was disabled in !875 because lcov didn't support the new coverage format produced by gcc9+. The latest lcov release in MSYS2 supports it again, so re-enable everything. lcov now writes native Windows paths to its output so adjust the path fixup script to handle those.
2020-09-30 11:36:49 +02:00
lcov \
ci/test-msys2: use $MINGW_PACKAGE_PREFIX
2022-10-29 02:29:38 +02:00
"${MINGW_PACKAGE_PREFIX}"-ccache \
"${MINGW_PACKAGE_PREFIX}"-gettext \
"${MINGW_PACKAGE_PREFIX}"-libffi \
"${MINGW_PACKAGE_PREFIX}"-meson \
"${MINGW_PACKAGE_PREFIX}"-pcre2 \
"${MINGW_PACKAGE_PREFIX}"-python3 \
"${MINGW_PACKAGE_PREFIX}"-python-pip \
"${MINGW_PACKAGE_PREFIX}"-toolchain \
"${MINGW_PACKAGE_PREFIX}"-zlib \
"${MINGW_PACKAGE_PREFIX}"-libelf
gitlab-ci: Add 32bit MinGW jobs using MSYS2 This builds glib using meson/ninja/ccache with mingw-w64 on a Windows machine. The CI scripts expect a gitlab runner to exist with the "win32" tag which uses the default "cmd" shell by default. Before running the tests pacman is invoked to update the system (potentially including bash etc, thus the extra step) Then a login shell is started with CHERE_INVOKING to not change the cwd and finally the test script is executed. https://bugzilla.gnome.org/show_bug.cgi?id=793729
2018-02-22 19:37:16 +01:00
CI: Include coverage data of code which isn't executed by the test suite. See comment in !151. Using the "--initial" option of lcov we collect the coverage of all compiled files and merge them later into the final report. This way we can see which files are built but never executed by the test suite. Because the --initial switch also collects files in the ccache directory we have to point it to the build directory instead, which in turn breaks --no-external. Instead of using --no-external in the collection step, filter out any files not in the source tree in the final coverage job through a path filter.
2018-07-06 09:33:22 +02:00
mkdir -p _coverage
gitlab-ci: Add 32bit MinGW jobs using MSYS2 This builds glib using meson/ninja/ccache with mingw-w64 on a Windows machine. The CI scripts expect a gitlab runner to exist with the "win32" tag which uses the default "cmd" shell by default. Before running the tests pacman is invoked to update the system (potentially including bash etc, thus the extra step) Then a login shell is started with CHERE_INVOKING to not change the cwd and finally the test script is executed. https://bugzilla.gnome.org/show_bug.cgi?id=793729
2018-02-22 19:37:16 +01:00
mkdir -p _ccache
ci: Fix various shellcheck warnings in the shell scripts I haven’t tested any of them. This is entirely mechanical. I used shellcheck 0.7.0 with default options. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2020-02-25 12:46:11 +01:00
CCACHE_BASEDIR="$(pwd)"
CCACHE_DIR="${CCACHE_BASEDIR}/_ccache"
export CCACHE_BASEDIR CCACHE_DIR
ci: Use Meson 1.0.0 on Windows and macOS CI builds This is a departure from our policy of using the minimum required Meson version, but I think it might be worth a try to see if it fixes the persistent intermittent build failures on these platforms due to what looks like build dependency graph issues. For example: - https://gitlab.gnome.org/GNOME/glib/-/jobs/2579411 - https://gitlab.gnome.org/GNOME/glib/-/jobs/2578792 - https://gitlab.gnome.org/GNOME/glib/-/jobs/2579220 - https://gitlab.gnome.org/pwithnall/glib/-/jobs/2588507 I was looking at trying to diagnose some of these failures in order to potentially file bugs against Meson, but the first step is really to test against the latest version of Meson. So here we are. Crucially, our other CI jobs continue to use the minimum Meson version required by GLib, so we continue to test that GLib builds with its minimum dependencies. I do not plan to change that. Also crucially, this MR continues to use a specific Meson version, rather than asking `pip` to install the latest available. Doing that could lead to unexpected regressions in future, and that’s not what GLib’s CI is meant to be testing for. Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
2023-02-16 14:29:54 +01:00
pip3 install --upgrade --user meson==1.0.0
ci: Fix various shellcheck warnings in the shell scripts I haven’t tested any of them. This is entirely mechanical. I used shellcheck 0.7.0 with default options. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2020-02-25 12:46:11 +01:00
CI: Make sure we use meson 0.49.2 in MSYS2 pip in MSYS2 seems to install scripts into $USERPROFILE instead of $HOME which means the MSYS2 meson, which is newer, wins. Make sure $USERPROFILE is in PATH as well.
2020-05-06 21:54:35 +02:00
PATH="$(cygpath "$USERPROFILE")/.local/bin:$HOME/.local/bin:$PATH"
CI: Include coverage data of code which isn't executed by the test suite. See comment in !151. Using the "--initial" option of lcov we collect the coverage of all compiled files and merge them later into the final report. This way we can see which files are built but never executed by the test suite. Because the --initial switch also collects files in the ccache directory we have to point it to the build directory instead, which in turn breaks --no-external. Instead of using --no-external in the collection step, filter out any files not in the source tree in the final coverage job through a path filter.
2018-07-06 09:33:22 +02:00
DIR="$(pwd)"
ci: Fix various shellcheck warnings in the shell scripts I haven’t tested any of them. This is entirely mechanical. I used shellcheck 0.7.0 with default options. Signed-off-by: Philip Withnall <withnall@endlessm.com>
2020-02-25 12:46:11 +01:00
export PATH CFLAGS
gitlab-ci: Add 32bit MinGW jobs using MSYS2 This builds glib using meson/ninja/ccache with mingw-w64 on a Windows machine. The CI scripts expect a gitlab runner to exist with the "win32" tag which uses the default "cmd" shell by default. Before running the tests pacman is invoked to update the system (potentially including bash etc, thus the extra step) Then a login shell is started with CHERE_INVOKING to not change the cwd and finally the test script is executed. https://bugzilla.gnome.org/show_bug.cgi?id=793729
2018-02-22 19:37:16 +01:00
ci: Add an msys2-clang64 job to run only on schedules It has enough particularities to require a job to monitor failures
2022-10-29 04:14:29 +02:00
if [[ "$MSYSTEM" == "CLANG64" ]]; then
# FIXME: fix the clang build warnings
# shellcheck disable=SC2086
meson ${MESON_COMMON_OPTIONS} _build
else
# shellcheck disable=SC2086
meson ${MESON_COMMON_OPTIONS} --werror _build
fi
gitlab-ci: Add 32bit MinGW jobs using MSYS2 This builds glib using meson/ninja/ccache with mingw-w64 on a Windows machine. The CI scripts expect a gitlab runner to exist with the "win32" tag which uses the default "cmd" shell by default. Before running the tests pacman is invoked to update the system (potentially including bash etc, thus the extra step) Then a login shell is started with CHERE_INVOKING to not change the cwd and finally the test script is executed. https://bugzilla.gnome.org/show_bug.cgi?id=793729
2018-02-22 19:37:16 +01:00
cd _build
ninja
ci: Set CFLAGS on msys2-mingw32 in yaml file as it happens for other jobs Be consistent, and based on this also perform the lcov job or not
2022-10-29 04:12:21 +02:00
if [[ "$CFLAGS" == *"-coverage"* ]]; then
lcov \
--quiet \
--config-file "${DIR}"/.lcovrc \
--directory "${DIR}/_build" \
--capture \
--initial \
--output-file "${DIR}/_coverage/${CI_JOB_NAME}-baseline.lcov"
fi
CI: Include coverage data of code which isn't executed by the test suite. See comment in !151. Using the "--initial" option of lcov we collect the coverage of all compiled files and merge them later into the final report. This way we can see which files are built but never executed by the test suite. Because the --initial switch also collects files in the ccache directory we have to point it to the build directory instead, which in turn breaks --no-external. Instead of using --no-external in the collection step, filter out any files not in the source tree in the final coverage job through a path filter.
2018-07-06 09:33:22 +02:00
ci: Use verbose output in meson by default Now that we're using TAP parsing, this will show subtest failures in details but without showing any logging error, that we'd still need to parse from actual logs.
2023-01-20 15:41:17 +01:00
meson test -v --timeout-multiplier "${MESON_TEST_TIMEOUT_MULTIPLIER}"
meson test -v --timeout-multiplier "${MESON_TEST_TIMEOUT_MULTIPLIER}" \
meson, ci: Support tests that can fail under certain conditions We have tests that are failing in some environments, but it's difficult to handle them because: - for some environments we just allow all the tests to fail: DANGEROUS - when we don't allow failures we have flacky tests: A CI pain So, to avoid this and ensure that: - New failing tests are tracked in all platforms - gitlab integration on tests reports is working - coverage is reported also for failing tests Add support for `can_fail` keyword on tests that would mark the test as part of the `failing` test suite. Not adding the suite directly when defining the tests as this is definitely simpler and allows to define conditions more clearly (see next commits). Now, add a default test setup that does not run the failing and flaky tests by default (not to bother distributors with testing well-known issues) and eventually run all the tests in CI: - Non-flaky tests cannot fail in all platforms - Failing and Flaky tests can fail In both cases we save the test reports so that gitlab integration is preserved.
2022-10-19 20:08:15 +02:00
--setup=unstable_tests --suite=failing --suite=flaky || true
ci: collect test coverage and deploy a html report through gitlab pages Use lcov for both Fedora and MSYS2 to create coverage reports and add a second ci stage which merges the coverage and creates a html report using genhtml. In the final stage, which is only run on master, the result is published on gitlab pages. https://bugzilla.gnome.org/show_bug.cgi?id=795636
2018-04-27 17:04:52 +02:00
ci: Set CFLAGS on msys2-mingw32 in yaml file as it happens for other jobs Be consistent, and based on this also perform the lcov job or not
2022-10-29 04:12:21 +02:00
if [[ "$CFLAGS" == *"-coverage"* ]]; then
lcov \
--quiet \
--config-file "${DIR}"/.lcovrc \
--directory "${DIR}/_build" \
--capture \
--output-file "${DIR}/_coverage/${CI_JOB_NAME}.lcov"
fi
Reference in New Issue Copy Permalink