summaryrefslogtreecommitdiffstats
path: root/tests/test-logging.c
Commit message (Collapse)AuthorAgeFilesLines
* test-logging: unset G_MESSAGES_DEBUGMarc-André Lureau2016-03-101-0/+1
| | | | | | | | This test is sensitive to G_MESSAGES_DEBUG variable. Make it insensitive by unsetting the environment variable. Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> Acked-by: Frediano Ziglio <fziglio@redhat.com>
* log: Add test case for logging codeChristophe Fergeau2016-01-261-0/+408
This gives us a baseline of how the SPICE/glib integration is supposed to behave. Everything goes through glib logging facilities, and is impacted by G_MESSAGES_DEBUG/G_DEBUG=fatal-{warnings,criticals} Messages in the SPICE_LOG_DOMAIN log domain (output either through spice_log() or g_log()) will also consider the legacy SPICE_DEBUG_LEVEL and SPICE_ABORT_LEVEL environment variables. Messages in other domains will not be impacted by these legacy environment variables. If spice-common is built without SPICE_DISABLE_ABORT, spice_return_if_fail()/spice_critical() will abort the program. g_return_if_fail()/g_critical() will not abort the program.