diff options
author | Matthias Clasen <mclasen@redhat.com> | 2022-01-18 07:24:44 -0500 |
---|---|---|
committer | Matthias Clasen <mclasen@redhat.com> | 2022-01-21 00:29:44 -0500 |
commit | 446ec7396b434911ee9d14bcc7df89f8b302bfcd (patch) | |
tree | f36ffbf1c1612908e3ce0cb378fd2432155789ac /tests/testboundaries_ucd.c | |
parent | 5b3990d18d744170e2fb84b88875080f540bef8b (diff) | |
download | pango-446ec7396b434911ee9d14bcc7df89f8b302bfcd.tar.gz |
Quiet down break tests
The output from the testboundaries tests just
overwhelms the test reports and makes it hard
to find the actual problems. Stop that.
You can still get the noise, by passing --verbose
to the tests.
Diffstat (limited to 'tests/testboundaries_ucd.c')
-rw-r--r-- | tests/testboundaries_ucd.c | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/tests/testboundaries_ucd.c b/tests/testboundaries_ucd.c index 8abf0b7a..bcc7ed45 100644 --- a/tests/testboundaries_ucd.c +++ b/tests/testboundaries_ucd.c @@ -239,7 +239,7 @@ do_test (const gchar *filename, g_assert_no_error (error); - g_test_message ("Filename: %s", filename); + if (g_test_verbose ()) g_test_message ("Filename: %s", filename); i = 1; for (;;) @@ -268,7 +268,7 @@ do_test (const gchar *filename, break; } - g_test_message ("Parsing line: %s", line); + if (g_test_verbose ()) g_test_message ("Parsing line: %s", line); g_assert_true (parse_line (line, bits, &string, &expected_attrs, &num_attrs)); if (num_attrs > 0) @@ -290,10 +290,10 @@ do_test (const gchar *filename, comments = (char *)""; } - g_test_message ("%s: line %d failed", filename, i); - g_test_message (" expected: %s", line); - g_test_message (" returned: %s", str); - g_test_message (" comments: %s", comments); + if (g_test_verbose ()) g_test_message ("%s: line %d failed", filename, i); + if (g_test_verbose ()) g_test_message (" expected: %s", line); + if (g_test_verbose ()) g_test_message (" returned: %s", str); + if (g_test_verbose ()) g_test_message (" comments: %s", comments); g_free (str); failed = TRUE; |