[tracker/sam/tracker-2.3-developer-experience: 8/38] ci: Allow controlling verbosity of tests in CI
- From: Sam Thursfield <sthursfield src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [tracker/sam/tracker-2.3-developer-experience: 8/38] ci: Allow controlling verbosity of tests in CI
- Date: Wed, 2 Oct 2019 20:17:59 +0000 (UTC)
commit 7cb67591a02bce9feced93eeff8e7224b9f157ff
Author: Sam Thursfield <sam afuera me uk>
Date: Tue Sep 10 11:13:36 2019 +0200
ci: Allow controlling verbosity of tests in CI
There is also a MESON_TEST_EXTRA_ARGS variable which can be set to cause
only one test to execute. This is to help with debugging test failures
that can only be reproduced on the CI runners.
.gitlab-ci.yml | 21 ++++++++++++++++++++-
HACKING.md | 5 +++++
2 files changed, 25 insertions(+), 1 deletion(-)
---
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 87e32d5ee..0ab47e694 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -1,3 +1,12 @@
+variables:
+ # These can be used to see verbose log output from the functional-tests.
+ # See HACKING.md for more information.
+ TRACKER_VERBOSITY: "0"
+ TRACKER_TESTS_VERBOSE: "no"
+
+ # This can be used when debugging test failures that only occur within GitLab CI.
+ MESON_TEST_EXTRA_ARGS: ""
+
stages:
- test
@@ -15,7 +24,17 @@ test-fedora-latest:
# screenful of junk each time unless we strip these.
unset $(env|grep -o '^CI_[^=]*')
- su tracker -c 'cd build; meson test --print-errorlogs'
+ su tracker -c 'cd build; meson test --print-errorlogs ${MESON_TEST_EXTRA_ARGS}'
+
+ after_script:
+ - |
+ echo "Test suite settings:"
+ echo
+ echo " TRACKER_VERBOSITY: ${TRACKER_VERBOSITY}"
+ echo " TRACKER_TESTS_VERBOSE: ${TRACKER_TESTS_VERBOSE}"
+ echo " MESON_TEST_EXTRA_ARGS: ${MESON_TEST_EXTRA_ARGS}"
+ echo
+ echo "These values can be set at https://gitlab.gnome.org/GNOME/tracker/pipelines/new"
artifacts:
when: always
diff --git a/HACKING.md b/HACKING.md
index 389b9c2a1..b907f3112 100644
--- a/HACKING.md
+++ b/HACKING.md
@@ -25,6 +25,11 @@ Tracker processes. Anything written directly to stdout, for example by
`g_print()` or by the dbus-daemon itself, will not be displayed unless
`TRACKER_TESTS_VERBOSE` is set.
+When working with GitLab CI, you can use the
+[Run Pipeline dialog](https://gitlab.gnome.org/GNOME/tracker/pipelines/new)
+to set the values of these variables and increase the verbosity of the tests in
+CI.
+
# Attaching a debugger to Tracker daemons
Tracker daemons are not started directly. Instead they are started by the D-Bus
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]