AuroraMiddleware/gtk2
1
0
Fork 0
forked from AuroraMiddleware/gtk
Code Issues Pull Requests Projects Releases Wiki Activity
e581c148d9
gtk2/.gitlab-ci/test-docker.sh

57 lines
1.1 KiB
Bash
Raw Normal View History

Add gitlab-ci support using a prebuilt docker image
2018-02-13 16:21:18 +00:00
#!/bin/bash
set -e
ci: Update the configuration options The options were renamed in commit 7b32900c5574.
2018-03-01 10:08:27 +00:00
srcdir=$(pwd)
gitlab-ci: Reenable ccache but disable it during the initial meson call There where some problems (??) with ccache not detecting changes during meson checks. Setting CCACHE_DISABLE during the meson execution makes ccache not use the cache and pass things directly to the compiler.
2018-04-11 10:18:55 +00:00
mkdir -p _ccache
export CCACHE_BASEDIR="$(pwd)"
export CCACHE_DIR="${CCACHE_BASEDIR}/_ccache"
ccache --zero-stats
ccache --show-stats
export CCACHE_DISABLE=true
ci: Update the configuration options The options were renamed in commit 7b32900c5574.
2018-03-01 10:08:27 +00:00
meson \
-Dx11-backend=true \
-Dwayland-backend=true \
-Dbroadway-backend=true \
build: disable Vulkan by default We don't want people to build Vulkan support when they just want to get GTK built. This is in particular true for GTK as a CI subproject or for people using jhbuild. Worse, just having Vulkan support compiled in tends to cause crashes in the Inspector, even if you are not using it.
2021-04-01 16:08:19 +00:00
-Dvulkan=enabled \
ci: Build with profiler support This will let us run sysprof-based performance tests.
2020-01-21 23:20:05 +00:00
-Dprofiler=true \
CI: Build with --werror This turns on --werror in the Fedora CI builds.
2019-04-17 16:53:53 +00:00
--werror \
Try building static libs on CI
2019-11-11 19:11:16 +00:00
${EXTRA_MESON_FLAGS:-} \
ci: Update the configuration options The options were renamed in commit 7b32900c5574.
2018-03-01 10:08:27 +00:00
_build $srcdir
gitlab-ci: Reenable ccache but disable it during the initial meson call There where some problems (??) with ccache not detecting changes during meson checks. Setting CCACHE_DISABLE during the meson execution makes ccache not use the cache and pass things directly to the compiler.
2018-04-11 10:18:55 +00:00
unset CCACHE_DISABLE
ci: Update the configuration options The options were renamed in commit 7b32900c5574.
2018-03-01 10:08:27 +00:00
cd _build
Add gitlab-ci support using a prebuilt docker image
2018-02-13 16:21:18 +00:00
ninja
gitlab-ci: Reenable ccache but disable it during the initial meson call There where some problems (??) with ccache not detecting changes during meson checks. Setting CCACHE_DISABLE during the meson execution makes ccache not use the cache and pass things directly to the compiler.
2018-04-11 10:18:55 +00:00
ccache --show-stats
gitlab-ci: run parts of the test suite This runs the tests in testsuite/{css,gtk,tools} All others suites have failing tests and need more work.
2018-02-17 10:55:40 +00:00
ci: Call the report script on failure as well GitLab's CI will bail out at the first failure, which means the JSON-to-JUnit conversion script won't run unless it's part of the same script that we run for building an testing.
2019-04-05 18:29:58 +00:00
set +e
gitlab-ci: run parts of the test suite This runs the tests in testsuite/{css,gtk,tools} All others suites have failing tests and need more work.
2018-02-17 10:55:40 +00:00
xvfb-run -a -s "-screen 0 1024x768x24" \
meson test \
CI: set a timeout multiplier for the tests CI can be slower than your normal dev machine so give it a bit more time
2019-03-26 15:37:22 +00:00
--timeout-multiplier 2 \
gitlab-ci: run parts of the test suite This runs the tests in testsuite/{css,gtk,tools} All others suites have failing tests and need more work.
2018-02-17 10:55:40 +00:00
--print-errorlogs \
ci: Update the test suite name The project name is "gtk", not "gtk+".
2019-02-08 10:49:24 +00:00
--suite=gtk \
--no-suite=gtk:a11y
ci: Call the report script on failure as well GitLab's CI will bail out at the first failure, which means the JSON-to-JUnit conversion script won't run unless it's part of the same script that we run for building an testing.
2019-04-05 18:29:58 +00:00
# Save the exit code
exit_code=$?
ci: Add an HTML report generator The JUnit cover report is useful, but only up to a point; for instance, it's not used unless it's part of a merge request. This means you don't get a report if you're pushing to a branch that does not have an MR open. With a simple Python script and some minimal templating, we can generate an HTML report from the "I Can't Believe it's not JSON™" log that Meson produces, and keep it as a CI artifact.
2019-04-13 13:11:30 +00:00
# We always want to run the report generators
ci: Call the report script on failure as well GitLab's CI will bail out at the first failure, which means the JSON-to-JUnit conversion script won't run unless it's part of the same script that we run for building an testing.
2019-04-05 18:29:58 +00:00
$srcdir/.gitlab-ci/meson-junit-report.py \
--project-name=gtk \
--job-id="${CI_JOB_NAME}" \
--output=report.xml \
meson-logs/testlog.json
ci: Add an HTML report generator The JUnit cover report is useful, but only up to a point; for instance, it's not used unless it's part of a merge request. This means you don't get a report if you're pushing to a branch that does not have an MR open. With a simple Python script and some minimal templating, we can generate an HTML report from the "I Can't Believe it's not JSON™" log that Meson produces, and keep it as a CI artifact.
2019-04-13 13:11:30 +00:00
$srcdir/.gitlab-ci/meson-html-report.py \
--project-name=GTK \
--job-id="${CI_JOB_NAME}" \
ci: Style the test report My web design skills are terrible, but it's better than nothing; I'm sure this will lead to somebody filing a merge request to make the test report look a lot better. While we're at it, let's include the reftest images inside the report itself, so we don't have to hunt them down.
2019-04-14 19:29:14 +00:00
--reftest-output-dir="testsuite/reftests/output" \
ci: Add an HTML report generator The JUnit cover report is useful, but only up to a point; for instance, it's not used unless it's part of a merge request. This means you don't get a report if you're pushing to a branch that does not have an MR open. With a simple Python script and some minimal templating, we can generate an HTML report from the "I Can't Believe it's not JSON™" log that Meson produces, and keep it as a CI artifact.
2019-04-13 13:11:30 +00:00
--output=report.html \
meson-logs/testlog.json
ci: Call the report script on failure as well GitLab's CI will bail out at the first failure, which means the JSON-to-JUnit conversion script won't run unless it's part of the same script that we run for building an testing.
2019-04-05 18:29:58 +00:00
exit $exit_code
Reference in New Issue Copy Permalink