changeset
Use fatal asserts unconditionally in the test code. Perhaps this could be better integrated in some way, but this works.
Fri, 27 Apr 2007 18:16:43 +0000
- author
- Richard Laager <rlaager@pidgin.im>
- date
- Fri, 27 Apr 2007 18:16:43 +0000
- changeset 16594
- d7ba74322ca4
- parent 16593
- 7fec4648661f
- child 16595
- edbcbb0b97b3
Use fatal asserts unconditionally in the test code. Perhaps this could be better integrated in some way, but this works.
| libpurple/tests/check_libpurple.c | file | annotate | diff | comparison | revisions |
--- a/libpurple/tests/check_libpurple.c Fri Apr 27 18:07:24 2007 +0000 +++ b/libpurple/tests/check_libpurple.c Fri Apr 27 18:16:43 2007 +0000 @@ -54,7 +54,14 @@ int main(void) { int number_failed; - SRunner *sr = srunner_create (master_suite()); + SRunner *sr; + + /* Make g_return_... functions fatal, ALWAYS. + * As this is the test code, this is NOT controlled + * by PURPLE_FATAL_ASSERTS. */ + g_log_set_always_fatal(G_LOG_LEVEL_CRITICAL); + + sr = srunner_create (master_suite()); srunner_add_suite(sr, cipher_suite()); srunner_add_suite(sr, jabber_jutil_suite());
