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 768853 - glib-2.48.1 - test failure: regex
glib-2.48.1 - test failure: regex
Status: RESOLVED DUPLICATE of bug 768677
Product: glib
Classification: Platform
Component: gregex
2.48.x
Other Linux
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2016-07-15 17:39 UTC by tka
Modified: 2016-07-17 22:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
glib/tests/test-suite.log (5.48 KB, text/plain)
2016-07-15 17:39 UTC, tka
Details

Description tka 2016-07-15 17:39:47 UTC
Created attachment 331606 [details]
glib/tests/test-suite.log

ERROR: regex
============

**
ERROR:/var/tmp/portage/dev-libs/glib-2.48.1/work/glib-2.48.1/glib/tests/regex.c:82:test_new: assertion failed (g_regex_get_compile_flags (regex) == data->real_compile_opts): (0x00000000 == 0x00000001)
/var/tmp/portage/dev-libs/glib-2.48.1/work/glib-2.48.1/tap-test: line 5: 21842 Aborted                 $1 -k --tap
# random seed: R02Sda2d573ba3ac6bf9e51ae516d482b36d
1..572
# Start of regex tests
ok 1 /regex/properties
PASS: regex 1 /regex/properties
ok 2 /regex/class
PASS: regex 2 /regex/class
ok 3 /regex/lookahead
PASS: regex 3 /regex/lookahead
ok 4 /regex/lookbehind
PASS: regex 4 /regex/lookbehind
ok 5 /regex/subpattern
PASS: regex 5 /regex/subpattern
ok 6 /regex/condition
PASS: regex 6 /regex/condition
ok 7 /regex/recursion
PASS: regex 7 /regex/recursion
# Bug Reference: http://bugzilla.gnome.org/640489
ok 8 /regex/multiline
PASS: regex 8 /regex/multiline
ok 9 /regex/explicit-crlf
PASS: regex 9 /regex/explicit-crlf
ok 10 /regex/max-lookbehind
PASS: regex 10 /regex/max-lookbehind
# Start of new tests
ok 11 /regex/new/1
PASS: regex 11 /regex/new/1
ok 12 /regex/new/2
PASS: regex 12 /regex/new/2
ok 13 /regex/new/3
PASS: regex 13 /regex/new/3
ok 14 /regex/new/4
PASS: regex 14 /regex/new/4
ok 15 /regex/new/5
PASS: regex 15 /regex/new/5
ok 16 /regex/new/6
PASS: regex 16 /regex/new/6
ok 17 /regex/new/7
PASS: regex 17 /regex/new/7
ok 18 /regex/new/8
PASS: regex 18 /regex/new/8
ok 19 /regex/new/9
PASS: regex 19 /regex/new/9
ok 20 /regex/new/10
PASS: regex 20 /regex/new/10
ok 21 /regex/new/11
PASS: regex 21 /regex/new/11
ok 22 /regex/new/12
PASS: regex 22 /regex/new/12
ok 23 /regex/new/13
PASS: regex 23 /regex/new/13
# End of new tests
# Start of new-check-flags tests
ok 24 /regex/new-check-flags/14
PASS: regex 24 /regex/new-check-flags/14
ok 25 /regex/new-check-flags/15
PASS: regex 25 /regex/new-check-flags/15
# ERROR:/var/tmp/portage/dev-libs/glib-2.48.1/work/glib-2.48.1/glib/tests/regex.c:82:test_new: assertion failed (g_regex_get_compile_flags (regex) == data->real_compile_opts): (0x00000000 == 0x00000001)
ERROR: regex - too few tests run (expected 572, got 25)
ERROR: regex - exited with status 134 (terminated by signal 6?)
Comment 1 Matthias Clasen 2016-07-15 17:47:31 UTC
Filing bugs about test failures is about marginal use - we see those test failures all the time anyway.
Comment 2 Matthias Clasen 2016-07-17 22:17:35 UTC

*** This bug has been marked as a duplicate of bug 768677 ***