reftest: Avoid assertions being compiled out

Calling functions inside a g_assert() means those functions will be
compiled out when building with G_DISABLE_ASSERT.

This fixes the release job in the CI pipeline.

diff --git a/testsuite/reftests/gtk-reftest.c b/testsuite/reftests/gtk-reftest.c
index 1dd1a080f210800842f719dd7aafb8554c482071..4d3d57db4a9ff43417b00627b51c92a766e1985e 100644 (file)
--- a/testsuite/reftests/gtk-reftest.c
+++ b/testsuite/reftests/gtk-reftest.c
@@ -551,8 +551,15 @@ main (int argc, char **argv)
   /* We need to ensure the process' current working directory
    * is the same as the reftest data, because we're using the
    * "file" property of GtkImage as a relative path in builder files.
+   *
+   * The g_assert() is needed to ensure GNU libc does not complain
+   * about the unused return value, and the G_GNUC_UNUSED is needed
+   * to avoid compiler warnings when g_assert() is compiled out
+   * during the release build.
    */
-  g_assert (chdir (basedir) == 0);
+  int res G_GNUC_UNUSED;
+  res = chdir (basedir);
+  g_assert (res == 0);
 
   g_log_set_writer_func (log_writer, NULL, NULL);