Commit b7e45448 authored by Sam Thursfield's avatar Sam Thursfield

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.
parent e13d9087
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
......
......@@ -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
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment