diff options
| author | Sam Thursfield <sam@afuera.me.uk> | 2019-09-10 11:13:36 +0200 |
|---|---|---|
| committer | Sam Thursfield <sam@afuera.me.uk> | 2019-09-14 12:42:05 +0200 |
| commit | b7e45448c34ca06095b5ceb51ae8a944cc1d2059 (patch) | |
| tree | 31226e7f91558d7f49264538806ab1c59cdeb315 | |
| parent | e13d9087af7ce4c601c4c2a4bda4083960eaf0c0 (diff) | |
| download | tracker-b7e45448c34ca06095b5ceb51ae8a944cc1d2059.tar.gz | |
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.
| -rw-r--r-- | .gitlab-ci.yml | 21 | ||||
| -rw-r--r-- | HACKING.md | 5 |
2 files changed, 25 insertions, 1 deletions
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index 1922acfb5..29a459acd 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 |