Summary: | dev-libs/glib-2.26.1-r1: test fail | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Pacho Ramos <pacho> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://bugzilla.gnome.org/show_bug.cgi?id=640412 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 339225 | ||
Attachments: |
build.log
build.log |
Description
Pacho Ramos
2011-01-22 21:54:59 UTC
Created attachment 260521 [details]
build.log
Umm, I see the following in dmesg when test fail: strfuncs[28580]: segfault at 0 ip 0000003601c7cb52 sp 00007fffc498a028 error 4 in libc-2.11.2.so[3601c00000+150000] strfuncs[2496]: segfault at 0 ip 0000003601c7cb52 sp 00007fff4619c168 error 4 in libc-2.11.2.so[3601c00000+150000] strfuncs[6614]: segfault at 0 ip 0000003601c7cb52 sp 00007fffa85f4d48 error 4 in libc-2.11.2.so[3601c00000+150000] strfuncs[12051]: segfault at 0 ip 0000003601c7cb52 sp 00007fffd4324848 error 4 in libc-2.11.2.so[3601c00000+150000] Created attachment 260523 [details]
build.log
And now:
/GDateTime/new_from_timeval: OK
/GDateTime/new_full: OK
/GDateTime/now: OK
/GDateTime/printf: **
ERROR:gdatetime.c:805:test_GDateTime_printf: assertion failed (__p == (t_str)): ("1256335200" == "1256421600")
FAIL
GTester: last random seed: R02S0284c8f5aaaefbb1ecd7f26bb0f4fdce
/bin/sh: línea 1: 7762 Terminado MALLOC_CHECK_=2 MALLOC_PERTURB_=$((${RANDOM:-256} % 256)) ../../glib/gtester --verbose testing option-context keyfile fileutils printf protocol rand strfuncs string markup-parse markup-coll
ect markup-escape markup-subparser array-test hostutils gvariant mem-overflow utils regex base64 sequence scannerapi shell collate utf8-pointer utf8-validate utf8-misc checksum hash date node convert list slist queue tree uri dir pattern
logging error bookmarkfile gdatetime
make[4]: *** [test-nonrecursive] Error 143
make[4]: Leaving directory `/var/tmp/portage/dev-libs/glib-2.26.1-r1/work/glib-2.26.1/glib/tests'
make[3]: *** [check-am] Error 2
make[3]: Leaving directory `/var/tmp/portage/dev-libs/glib-2.26.1-r1/work/glib-2.26.1/glib/tests'
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/dev-libs/glib-2.26.1-r1/work/glib-2.26.1/glib'
make[1]: *** [check] Error 2
make[1]: Leaving directory `/var/tmp/portage/dev-libs/glib-2.26.1-r1/work/glib-2.26.1/glib'
make: *** [check-recursive] Error 1
emake failed
And:
strfuncs[7977]: segfault at 0 ip 0000003601c7cb52 sp 00007fff72cb41a8 error 4 in libc-2.11.2.so[3601c00000+150000]
Maybe I should recompile glibc, but I don't know why it's causing problems now after months of working ok :-|
(In reply to comment #2) > Umm, I see the following in dmesg when test fail: > > strfuncs[28580]: segfault at 0 ip 0000003601c7cb52 sp 00007fffc498a028 error 4 > in libc-2.11.2.so[3601c00000+150000] > strfuncs[2496]: segfault at 0 ip 0000003601c7cb52 sp 00007fff4619c168 error 4 > in libc-2.11.2.so[3601c00000+150000] > strfuncs[6614]: segfault at 0 ip 0000003601c7cb52 sp 00007fffa85f4d48 error 4 > in libc-2.11.2.so[3601c00000+150000] > strfuncs[12051]: segfault at 0 ip 0000003601c7cb52 sp 00007fffd4324848 error 4 > in libc-2.11.2.so[3601c00000+150000] > Looks like these error are a bit "common" (see bug 311839), then, I don't know if they are related with this exact problem or not (In reply to comment #0) > PASS: contexts > TEST: gsettings... (pid=7943) > /gsettings/basic: ** > ERROR:gsettings.c:38:test_basic: assertion failed (str == "goodbye world"): > ("Hello, earthlings" == "goodbye world") > FAIL > GTester: last random seed: R02S36566b58312ae2f10bf618b442025703 > /bin/sh: línea 1: 7687 Terminado MALLOC_CHECK_=2 > MALLOC_PERTURB_=$((${RANDOM:-256} % 256)) ../../glib/gtester --verbose > memory-input-stream memory-output-stream readwrite g-file g-file-info > converter-stream data-input-stream data-output-stream g-icon > buffered-input-stream buffered-output-stream sleepy-stream filter-streams > volumemonitor simple-async-result srvtarget contexts gsettings gschema-compile > async-close-output-stream gdbus-addresses network-address gdbus-message socket > gdbus-connection gdbus-connection-slow gdbus-names gdbus-proxy > gdbus-proxy-well-known-name gdbus-introspection gdbus-threading gdbus-export > gdbus-error gdbus-peer gdbus-exit-on-close gdbus-non-socket gdbus-bz627724 > appinfo contenttype file live-g-file desktop-app-info unix-fd unix-streams > gdbus-serialization > make[4]: *** [test-nonrecursive] Error 143 > make[4]: Leaving directory > `/var/tmp/portage/dev-libs/glib-2.26.1-r1/work/glib-2.26.1/gio/tests' > make[3]: *** [check-am] Error 2 > make[3]: Leaving directory > `/var/tmp/portage/dev-libs/glib-2.26.1-r1/work/glib-2.26.1/gio/tests' > make[2]: *** [check-recursive] Error 1 > make[2]: Leaving directory > `/var/tmp/portage/dev-libs/glib-2.26.1-r1/work/glib-2.26.1/gio' > make[1]: *** [check] Error 2 > make[1]: Leaving directory > `/var/tmp/portage/dev-libs/glib-2.26.1-r1/work/glib-2.26.1/gio' > make: *** [check-recursive] Error 1 > emake failed > * ERROR: dev-libs/glib-2.26.1-r1 failed: > * tests failed > * > * Call stack: > * ebuild.sh, line 56: Called src_test > * environment, line 3392: Called die > * The specific snippet of code: > * emake check || die "tests failed" > * > * If you need support, post the output of 'emerge --info > =dev-libs/glib-2.26.1-r1', > * the complete build log and the output of 'emerge -pqv > =dev-libs/glib-2.26.1-r1'. > * The complete build log is located at > '/var/log/portage/build/dev-libs/glib-2.26.1-r1:20110122-214010.log'. > * The ebuild environment file is located at > '/var/tmp/portage/dev-libs/glib-2.26.1-r1/temp/environment'. > * S: '/var/tmp/portage/dev-libs/glib-2.26.1-r1/work/glib-2.26.1' > OK, I am able to reproduce this failure if I don't apply patch for fixing bug 351387 (In reply to comment #3) > Created an attachment (id=260523) [details] > build.log > > And now: > > /GDateTime/new_from_timeval: OK > /GDateTime/new_full: OK > /GDateTime/now: OK > /GDateTime/printf: ** > ERROR:gdatetime.c:805:test_GDateTime_printf: assertion failed (__p == (t_str)): > ("1256335200" == "1256421600") > FAIL > GTester: last random seed: R02S0284c8f5aaaefbb1ecd7f26bb0f4fdce > /bin/sh: línea 1: 7762 Terminado MALLOC_CHECK_=2 > MALLOC_PERTURB_=$((${RANDOM:-256} % 256)) ../../glib/gtester --verbose testing > option-context keyfile fileutils printf protocol rand strfuncs string > markup-parse markup-coll > ect markup-escape markup-subparser array-test hostutils gvariant mem-overflow > utils regex base64 sequence scannerapi shell collate utf8-pointer utf8-validate > utf8-misc checksum hash date node convert list slist queue tree uri dir pattern > logging error bookmarkfile gdatetime > make[4]: *** [test-nonrecursive] Error 143 > make[4]: Leaving directory > `/var/tmp/portage/dev-libs/glib-2.26.1-r1/work/glib-2.26.1/glib/tests' > make[3]: *** [check-am] Error 2 > make[3]: Leaving directory > `/var/tmp/portage/dev-libs/glib-2.26.1-r1/work/glib-2.26.1/glib/tests' > make[2]: *** [check-recursive] Error 1 > make[2]: Leaving directory > `/var/tmp/portage/dev-libs/glib-2.26.1-r1/work/glib-2.26.1/glib' > make[1]: *** [check] Error 2 > make[1]: Leaving directory > `/var/tmp/portage/dev-libs/glib-2.26.1-r1/work/glib-2.26.1/glib' > make: *** [check-recursive] Error 1 > emake failed And I am able to reproduce this one if I apply patch for bug 351387 I don't have time now, but I need to try: http://git.gnome.org/browse/glib/commit/?id=3f059a6a123dd62257f224b9af7701078783060e (and maybe setting LC_ALL=C for other tests could be needed also) gsettings/basic test fails due GSETTINGS_BACKEND variable set to "gconf", this explains why I didn't hit this issue before as I was still using gconf-2.32.0 until a few days ago resetting the variable to "memory" in the ebuild should do the trick then. + 24 Jan 2011; Pacho Ramos <pacho@gentoo.org> glib-2.26.1-r1.ebuild, + +files/glib-2.26.1-gatomic-header.patch, + +files/glib-2.26.1-gdatetime-test.patch: + Add openbsd patch to fix build on several arches (bug #351387 by Alan + Hourihane and Raúl Porcel) once I confirmed it doesn't cause any test + failure regression. Remove test that seems to fail depending on time of day + as done by upstream (was causing one of the failures in bug #352451) and + unset GSETTINGS_BACKEND (bug #352451) until upstream takes care (upstream bug + #640412). + (In reply to comment #8) > resetting the variable to "memory" in the ebuild should do the trick then. > Sorry, (mid-air collision), I finally opted for unsetting variable, do you think would be better to set it to "memory" instead? Important comment from upstream: https://bugzilla.gnome.org/show_bug.cgi?id=640412#c1 "The gconf backend is not meant to be used at all except as a tool for porting applications. Please never set GSETTINGS_BACKEND=gconf in any kind of global way. This way lies pain." That should be dropped from gconf-2.32.0-r1 then? about setting the variable, setting it to memory or unsetting it should have the same effect. (In reply to comment #11) > Important comment from upstream: > https://bugzilla.gnome.org/show_bug.cgi?id=640412#c1 > "The gconf backend is not meant to be used at all except as a tool for porting > applications. > > Please never set GSETTINGS_BACKEND=gconf in any kind of global way. This way > lies pain." > > That should be dropped from gconf-2.32.0-r1 then? nope, upstream should have provided a full port to gsettings if they wished downstream to not use gconf anymore. Current settings seems to provide the same user experience we've had for years so we're not gonna change it just because "it isn't clean". We'll make it clean when it can actually be cleaned up. OK, thanks :-) |