After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 656127 - running tests leaves lots of coredumps
running tests leaves lots of coredumps
Status: RESOLVED OBSOLETE
Product: glib
Classification: Platform
Component: gtest
2.29.x
Other Linux
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2011-08-07 23:24 UTC by Yeti
Modified: 2018-05-24 13:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Yeti 2011-08-07 23:24:03 UTC 
If coredumps are enabled then running `make check' in GLib produces over 90 coredumps in various `tests' subdirectories even if all tests succeed.  This is due to forked tests that are expected to abort (which subsequently checked by g_test_trap_assert_failed()).

This is not specific to the GLib test suite; any gtester test suite containing tests that are supposed to abort will behave the same.

It is easy to disable coredumps, however, enabling them while running tests is useful in case something fails *unexpectedly*.  So the tests should dump core only if this unexpected failure happens and not when everything goes as expected.

Steps to reproduce:
1. git clone git://git.gnome.org/glib
2. cd glib
3. ./autogen.sh
4. make
5. make check
6. find . -name 'core*'

Expected results:
All tests pass and no coredumps are left.

Actual results:
All tests pass and 93 coredumps are left.
Comment 1 GNOME Infrastructure Team 2018-05-24 13:17:08 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glib/issues/436.