unigbrk/uc-is-grapheme-break tests: Reduce verbosity

[Bruno Haible]

The test-uc-is-grapheme-break.sh test produces a couple of numbers
in the log, that don't help understanding what the test is doing.
Better remove these traces.


2024-01-30  Bruno Haible  <bruno@clisp.org>

        unigbrk/uc-is-grapheme-break tests: Reduce verbosity.
        * tests/unigbrk/test-uc-is-grapheme-break.c
        (graphemebreakproperty_to_string): Don't print gbp to stdout.

diff --git a/tests/unigbrk/test-uc-is-grapheme-break.c 
b/tests/unigbrk/test-uc-is-grapheme-break.c
index 67c5c21680..b71035a2a9 100644
--- a/tests/unigbrk/test-uc-is-grapheme-break.c
+++ b/tests/unigbrk/test-uc-is-grapheme-break.c
@@ -30,7 +30,6 @@
 const char *
 graphemebreakproperty_to_string (int gbp)
 {
-  printf ("%d\n", gbp);
   switch (gbp)
     {
 #define CASE(VALUE) case GBP_##VALUE: return #VALUE;