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 693720 - glib-networking: test fails
glib-networking: test fails
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: network
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2013-02-13 15:56 UTC by Murray Cumming
Modified: 2013-02-13 19:21 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Murray Cumming 2013-02-13 15:56:36 UTC
On the Openismus Jenkins server (using glib from git master, on Ubuntu Quantal), "make check" fails on glib-networking from git master:

TEST: connection... (pid=15624)
  /tls/connection/basic:                                               OK
  /tls/connection/verified:                                            OK
  /tls/connection/client-auth:                                         OK
  /tls/connection/client-auth-rehandshake:                             **
GLib-Net:ERROR:connection.c:96:teardown_connection: assertion failed: (test->server_connection == NULL)
FAIL
GTester: last random seed: R02Saaee1c6dbf6e5f7a48133987cf07169d
/bin/bash: line 1: 15620 Terminated              gtester --verbose certificate file-database connection pkcs11-util pkcs11-array pkcs11-pin pkcs11-slot
make[2]: *** [test-nonrecursive] Error 143
make[2]: Leaving directory `/var/lib/jenkins/workspace/glib-networking/tls/tests'
make[1]: *** [check-am] Error 2
make[1]: Leaving directory `/var/lib/jenkins/workspace/glib-networking/tls/tests'
make: *** [check-recursive] Error 1
Build step 'Execute shell' marked build as failure
Archiving artifacts
Finished: FAILURE

You should be able to see the full build log here:
http://jenkins.openismus.com/job/glib-networking/8/console
Comment 1 Dan Winship 2013-02-13 18:37:57 UTC
This is just a race condition in the test program. I think it should
be fixed in master now, but reopen if it shows up again.
Comment 2 Murray Cumming 2013-02-13 19:21:00 UTC
Yes, that seems to fix it. Thanks.