Skip to content
GitLab

ci: Try reducing FD soft limit to fix valgrind tests

Philip Withnall requested to merge wip/pwithnall/try-fixing-valgrind-ci into main

They are currently failing with the error:

  1/273 glib:glib / array-test                                  FAIL             0.19s   killed by signal 11 SIGSEGV
05:04:16 G_DEBUG=gc-friendly G_TEST_BUILDDIR=/builds/GNOME/glib/_build/glib/tests MALLOC_CHECK_=2 MALLOC_PERTURB_=133 G_TEST_SRCDIR=/builds/GNOME/glib/glib/tests valgrind --tool=memcheck --error-exitcode=1 --track-origins=yes --leak-check=full --leak-resolution=high --num-callers=50 --show-leak-kinds=definite,possible --show-error-list=yes --suppressions=/builds/GNOME/glib/tools/glib.supp /builds/GNOME/glib/_build/glib/tests/array-test
----------------------------------- output -----------------------------------
stderr:

valgrind: m_libcfile.c:66 (vgPlain_safe_fd): Assertion 'newfd >= VG_(fd_hard_limit)' failed.
------------------------------------------------------------------------------

I’m not really sure what that means, but show-execution-environment.sh says the FD soft limit is set to 524288 on the CI machine. That seems high; on my machine it’s only 1024 (and the valgrind tests pass). So let’s try 1024.

The valgrind CI has been failing since we most recently upgraded the CI image to a new version of Fedora.

Signed-off-by: Philip Withnall pwithnall@endlessos.org

Merge request reports