| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
This seems cleaner now that we use TRACKER_DEBUG everywhere else.
|
|
|
|
| |
This outputs all queries to the console.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Users should now use G_MESSAGES_DEBUG=Tracker to see debug messages
on the console.
The TRACKER_VERBOSITY only worked if tracker_log_init() had been called,
which can't be done when libtracker-sparql is being used from an
application outside of Tracker.
|
|
|
|
|
|
|
|
| |
This works the same as GTK's GTK_DEBUG variable. It will
allow us to include more types of optional debugging info,
and will make the default debug output more readlable.
See https://gitlab.gnome.org/GNOME/tracker/issues/178
|
| |
|
| |
|
|
|
|
| |
This replaces the wiki page https://wiki.gnome.org/Projects/Tracker/Testing
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes https://gitlab.gnome.org/GNOME/tracker/issues/111 and also
simplifies the instructions in the README for running Tracker from
the build tree.
The sandbox utility is now executed from the top directory by running:
python3 -m utils.trackertestutils
Previously, due to importing stuff from trackertestutils. you needed to
run it from the utils/ directory or set PYTHONPATH appropriately.
Additionally, tracker-miners.git will ship a 'run-uninstalled' script
to provide convenient access to the sandbox script and allow running
Tracker from the build tree.
|
|
|
|
|
|
| |
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.
|
|
This talks about how to enable different kinds of logging output from
the functional tests, now that the previous commit has introduced some
sanity into the logging.
Attaching debugger is also discussed.
|