luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-11-10 03:16:17 +01:00
Code Issues Packages Projects Releases Wiki Activity
9635fd4e40
glib/.gitlab-ci/test-msys2.sh

62 lines
1.4 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
set -e
export PATH="/c/msys64/$MSYSTEM/bin:$PATH"
if [[ "$MSYSTEM" == "MINGW32" ]]; then
export MSYS2_ARCH="i686"
else
export MSYS2_ARCH="x86_64"
fi
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 \
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
mingw-w64-$MSYS2_ARCH-ccache \
mingw-w64-$MSYS2_ARCH-gettext \
mingw-w64-$MSYS2_ARCH-libffi \
mingw-w64-$MSYS2_ARCH-meson \
ci: Add libpcre2 dependencies and subproject This is in preparation for porting `GRegex` to libpcre2, which is happening in !2529. It’s a big port, though, and specially rebuilding the CI images to add libpcre2 for it is a pain. Add libpcre2, and then !2529 can drop the old libpcre dependencies when the port lands. Signed-off-by: Philip Withnall <pwithnall@endlessos.org> Helps: #1085
2022-06-24 13:50:26 +02:00
mingw-w64-$MSYS2_ARCH-pcre2 \
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
mingw-w64-$MSYS2_ARCH-python3 \
ci: Fix msys-mingw32 CI builds due to package rename Fix by Christoph Reiter, see https://gitlab.gnome.org/GNOME/glib/-/merge_requests/1879#note_1009843. Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
2021-01-19 10:00:54 +01:00
mingw-w64-$MSYS2_ARCH-python-pip \
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
mingw-w64-$MSYS2_ARCH-toolchain \
gresource-tool: fix build in case libelf is available on Windows. Fixes #1466 The gresource code uses libelf if available but that also depends on mmap but isn't guarded with HAVE_MMAP. This can make the build fail under MSYS2 where a mingw version of libelf exists but there is no mmap. Instead of guarting the libelf code with HAVE_LIBELF add a new macro named USE_LIBELF which is only defined if libelf and mmap support are available. Also install the mingw libelf version for CI so we catch similar errors in the future.
2018-08-01 18:54:01 +02:00
mingw-w64-$MSYS2_ARCH-zlib \
mingw-w64-$MSYS2_ARCH-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
build: Bump Meson dependency to 0.60.0 As per the new policy in `docs/meson-version.md`, we can now bump the dependency. Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
2022-05-05 20:23:20 +02:00
pip3 install --upgrade --user meson==0.60.3
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: 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
CFLAGS="-coverage -ftest-coverage -fprofile-arcs"
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: fix warnings and enable --werror for the mingw build Fix various warnings regarding unused variables, duplicated branches etc by adjusting the ifdeffery and some missing casts. gnulib triggers -Wduplicated-branches in one of the copied files, disable as that just makes updating the code harder. The warning indicating missing features are made none fatal through pragmas. They still show but don't abort the build. https://bugzilla.gnome.org/show_bug.cgi?id=793729
2018-04-25 16:07:59 +02:00
meson --werror --buildtype debug _build
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: 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 \
--quiet \
build: Move lcovrc file to root so it’s picked up by Meson Move the lcovrc file to the root of the project, so that it’s picked up by Meson when running `ninja coverage` locally. See https://github.com/mesonbuild/meson/issues/4628 This won’t affect the code coverage run on the CI, since that explicitly used the lcovrc file already. Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
2022-04-28 12:57:45 +02:00
--config-file "${DIR}"/.lcovrc \
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
--directory "${DIR}/_build" \
--capture \
--initial \
--output-file "${DIR}/_coverage/${CI_JOB_NAME}-baseline.lcov"
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
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
# FIXME: fix the test suite
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
meson test --timeout-multiplier "${MESON_TEST_TIMEOUT_MULTIPLIER}" --no-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: 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 \
--quiet \
build: Move lcovrc file to root so it’s picked up by Meson Move the lcovrc file to the root of the project, so that it’s picked up by Meson when running `ninja coverage` locally. See https://github.com/mesonbuild/meson/issues/4628 This won’t affect the code coverage run on the CI, since that explicitly used the lcovrc file already. Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
2022-04-28 12:57:45 +02:00
--config-file "${DIR}"/.lcovrc \
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
--directory "${DIR}/_build" \
--capture \
--output-file "${DIR}/_coverage/${CI_JOB_NAME}.lcov"
Reference in New Issue Copy Permalink