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 709628 - TLS installed tests have hardcoded path to certificate in build tree
TLS installed tests have hardcoded path to certificate in build tree
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: network
2.38.x
Other Linux
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2013-10-08 11:22 UTC by Iain Lane
Modified: 2013-10-08 20:29 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Iain Lane 2013-10-08 11:22:07 UTC 
The TLS installed tests don't work properly because the path to server.pem is hardcoded to a location in the build tree at compile time.

For Debian & Ubuntu I've packaged these tests so that we can automatically run them as part of systematic regression testing, but these tests fail as you can see:

/tls/certificate/create-pem: **
GLib-Net:ERROR:certificate.c:52:setup_certificate: assertion failed (error == NULL): Failed to open file '/build/buildd/glib-networking-2.38.0/tls/tests/files/server.pem': No such file or directory (g-file-error-quark, 4)
Test glib-networking/certificate.test failed: Child process killed by signal 6
[…]

https://jenkins.qa.ubuntu.com/view/Saucy/view/AutoPkgTest/job/saucy-adt-glib-networking/2/ARCH=i386,label=adt/consoleText

I think you need to use g_test_build_filename() and co (and make sure to install this file with the tests).
Comment 1 Dan Winship 2013-10-08 20:29:52 UTC 
oops. fixed in master