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 782237 - Test failure in fileutils tests on Mageia 6
Test failure in fileutils tests on Mageia 6
Status: RESOLVED INCOMPLETE
Product: glib
Classification: Platform
Component: build
2.53.x
Other Linux
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2017-05-05 18:40 UTC by Nikolai Malykh
Modified: 2018-02-14 10:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
test-suite.log (4.75 KB, text/x-log)
2017-05-05 18:40 UTC, Nikolai Malykh
Details
Test log (4.75 KB, text/plain)
2017-05-08 09:37 UTC, Nikolai Malykh
Details
core dumps files (83.42 KB, application/zip)
2017-05-08 09:47 UTC, Nikolai Malykh
Details

Description Nikolai Malykh 2017-05-05 18:40:35 UTC
Created attachment 351228 [details]
test-suite.log

make check error
Comment 1 Philip Withnall 2017-05-07 19:13:51 UTC
What OS and distribution is this on?

The relevant bits of the log are:

ERROR: fileutils
================

**
GLib:ERROR:fileutils.c:854:test_stdio_wrappers: assertion failed: (ret == -1)
# random seed: R02S550b3afe96898b049a667ba67ea5c8ab
1..15
# Start of fileutils tests
…
PASS: fileutils 14 /fileutils/read-link
../../tap-test: line 5: 27139 Аварийный останов         (core dumped) $1 -k --tap
# GLib:ERROR:fileutils.c:854:test_stdio_wrappers: assertion failed: (ret == -1)
ERROR: fileutils - too few tests run (expected 15, got 14)
ERROR: fileutils - exited with status 134 (terminated by signal 6?)
Comment 2 Nikolai Malykh 2017-05-07 20:24:03 UTC
Mageia 6
Comment 3 Philip Withnall 2017-05-07 20:34:35 UTC
Can you please apply this commit:
https://git.gnome.org/browse/glib/commit/?id=5c1e85669a90e8ffc4a2c3bf2b2fec71eb35014d
and rebuild, then reproduce the failure and attach the logs from it.

If you could also attach the core dump file from the test crash, that would be useful.
Comment 4 Nikolai Malykh 2017-05-08 09:37:41 UTC
Created attachment 351332 [details]
Test log
Comment 5 Nikolai Malykh 2017-05-08 09:47:19 UTC
Created attachment 351333 [details]
core dumps files

glib/tests/core.1.16140
glib/tests/mkdir-test/core.1.13477
Comment 6 Philip Withnall 2017-05-08 10:18:42 UTC
Are the tests running in a clean environment when you run them? Please make sure the glib/tests/mkdir-test directory does not exist before you run the tests. (I’m wondering if coredump files from previous failed test runs are causing the tests to continue to fail, spuriously.)
Comment 7 Nikolai Malykh 2017-05-08 15:20:17 UTC
(In reply to Philip Withnall from comment #6)
> Are the tests running in a clean environment when you run them? Please make
> sure the glib/tests/mkdir-test directory does not exist before you run the
> tests. (I’m wondering if coredump files from previous failed test runs are
> causing the tests to continue to fail, spuriously.)

Yes, the test running in a clean environment. Glib was built in the new directory.
Comment 8 Philip Withnall 2018-02-13 14:32:39 UTC
Sorry for the delay in getting back to this. Are you still having this issue with the latest GLib release? Nothing much has changed with file utilities, so I suspect you will be.

What file system are you building and running the tests on?

If you can still reproduce the crash, can you please attach a full backtrace from it (the `t a a bt` command in gdb). I can’t get those core files to work any more. Thanks.
Comment 9 Nikolai Malykh 2018-02-13 21:26:24 UTC
I cannot reproduce this crash now. It's been too long and I do not already have that version.
Comment 10 Philip Withnall 2018-02-14 10:45:03 UTC
So `make check` passes fine for you now? That’s great. If you do manage to reproduce the failure, please re-open this bug report. Thanks for getting back to me.