| Summary: | net-libs/glib-networking-2.30.1 intermittently fails tls test | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Xake <kanelxake> |
| Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | Keywords: | TESTFAILURE |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://bugzilla.gnome.org/show_bug.cgi?id=695062 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
build.log
gdb ./tls (had to run the file three times inside of gdb before it terminated) |
||
|
Description
Xake
2011-10-20 08:08:10 UTC
The changes that you proposed had already been made in the glib-networking-2.30.1-r1 ebuild, but are for now commented out, and the tests themselves disabled by RESTRICT="test", due to the intermittent failures in the tls test that I am also experiencing. On the other hand, another developer reported that he cannot reproduce those tls test failures. Leaving this bug open for now as a reminder to figure out what is going on with the tls tests. Yeah, that is the strange part. Sometime the tls test works, most of the time it does not, and this even with a identical env (i.e. ssh to the host, run "sudo emerge -1 glib-networking ; sudo emerge -1 glib-networking", and this time around the first one worked, the second time it failed. last time I tested it was the opposite). I do not know if there is some kind of race-condition triggered? I am the one that cannot reproduce :-/ Have you tried to run tests when manually compiling? ./configure && make && make check Are you able to reproduce that tls test failure? I have tried multiple times (~10) and it doesn't fail for me Created attachment 290493 [details] gdb ./tls (had to run the file three times inside of gdb before it terminated) (In reply to comment #3) > I am the one that cannot reproduce :-/ > > Have you tried to run tests when manually compiling? > ./configure && make && make check > > Are you able to reproduce that tls test failure? I have tried multiple times > (~10) and it doesn't fail for me For me it fails more often then it works... I did: tar xaf /var/portage/distfiles/glib-networking-2.30.1.tar.xz && cd glib-networking-2.30.1 && ./configure && make -j10 && make check For me the testcase works about three aout of 20 times. Does not matter if I recompile, or just runs the test over and over again, sometimes it works, most of the time it does not. Just running the test-file itself is just as good: xake@lillen ~/devel/glib-networking-2.30.1/tls/tests $ ./tls /tls/connection/basic: OK /tls/connection/verified: OK /tls/connection/client-auth: ** ERROR:tls.c:265:on_input_read_finish: assertion failed (error == NULL): Error performing TLS handshake: The request is invalid. (g-tls-error-quark, 1) Avbruten (SIGABRT) (minnesutskrift skapad) xake@lillen ~/devel/glib-networking-2.30.1/tls/tests $ ./tls /tls/connection/basic: OK /tls/connection/verified: OK /tls/connection/client-auth: ** ERROR:tls.c:265:on_input_read_finish: assertion failed (error == NULL): Error performing TLS handshake: The request is invalid. (g-tls-error-quark, 1) Avbruten (SIGABRT) (minnesutskrift skapad) xake@lillen ~/devel/glib-networking-2.30.1/tls/tests $ ./tls /tls/connection/basic: OK /tls/connection/verified: OK /tls/connection/client-auth: OK /tls/connection/client-auth-rehandshake: OK /tls/connection/no-database: OK /tls/connection/socket-client: OK /tls/connection/socket-client-failed: OK /tls/backend/default-database-is-singleton: OK /tls/certificate/create-destroy-pem: OK /tls/certificate/create-destroy-der: OK /tls/certificate/create-with-issuer: OK /tls/certificate/verify-good: OK /tls/certificate/verify-bad-identity: OK /tls/certificate/verify-bad-ca: OK /tls/certificate/verify-bad-before: OK /tls/certificate/verify-bad-expired: OK /tls/certificate/verify-bad-combo: OK /tls/database/verify-good: OK /tls/database/verify-bad-identity: OK /tls/database/verify-bad-ca: OK /tls/database/verify-bad-before: OK /tls/database/verify-bad-expired: OK /tls/database/verify-bad-combo: OK /tls/file-database/test-handle: OK /tls/file-database/test-handle-invalid: OK In that case, please report your test failures when manually compiling to upstream -> bugzilla.gnome.org Hopefully, they will help us to know where is the problem Thanks After some digging on my own machine it appears as if this is a problem with gnutls. For testing I upgraded to gnutls-2.12.12, and all of a sudden I could not reproduce the testfailure. I downgraded to 2.10.5 and the testfailure was back. The thing is: also the testsuite for gnutls-2.10 started failing for me in the same fashion while downgrading/after downgrading, something I cannot remember it ever doing before. So why gnutls have started to fail on my system, I am not so sure about. Maybe a dependency that has been bumped and older version of gnutls is unstable with? However, as you can see, the problem is not with glib-networking (and g-n-2.31 also needs >=gnutls-2.11). They are now skipped and upstream fixed the problem for 2.38 |
