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 728977 - Testsuite fails to run
Testsuite fails to run
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: network
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
: 727422 755928 758134 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2014-04-25 20:49 UTC by Gilles Dartiguelongue
Modified: 2017-08-23 09:38 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
build.log (28.67 KB, application/octet-stream)
2014-04-25 20:49 UTC, Gilles Dartiguelongue 		  Details
0001-test-connection-is-not-PKCS-11-related.patch (1.18 KB, patch)
2014-04-25 21:04 UTC, Gilles Dartiguelongue 		committed Details | Review

Description Gilles Dartiguelongue 2014-04-25 20:49:15 UTC 
Created attachment 275166 [details]
build.log

Hi,

this appears to be a regression over 2.38.2.
It fails both from 2.40.* release tarballs and master:

$ export LC_ALL="C"; git clean -fxd .; ( git status; git describe; ./autogen.sh; make -j16;  make check -j1 ) 2>&1 |tee build.log
Comment 1 Gilles Dartiguelongue 2014-04-25 20:53:06 UTC 
Also you might want to check why 2.40.2 tag points to the same commit as 2.34.2.
Comment 2 Gilles Dartiguelongue 2014-04-25 21:01:48 UTC 
Also you might want to check why 2.40.2 tag points to the same commit as 2.34.2.
Comment 3 Gilles Dartiguelongue 2014-04-25 21:03:23 UTC 
So to add a bit some confusion, I did have a problem with unittests but not this one.

When running configure with --without-pkcs11, unitttests would fail at the connection test because it is added to test_programs outside the ifdefs but it's sources are defined inside the ifdef.

Attaching a patch to solve that issue which is the only problem I am having with 2.40.* for now.
Comment 4 Gilles Dartiguelongue 2014-04-25 21:04:02 UTC 
Created attachment 275169 [details] [review]
0001-test-connection-is-not-PKCS-11-related.patch
Comment 5 Dan Winship 2014-04-25 21:09:58 UTC 
(In reply to comment #1)
> Also you might want to check why 2.40.2 tag points to the same commit as
> 2.34.2.

bug 684247 comment 1. Except that I fixed it later, and it doesn't show up in a fresh checkout, so I'm not sure why you're still seeing it. (Maybe "git fetch --prune" would help?)
Comment 6 Gilles Dartiguelongue 2014-04-25 21:27:30 UTC 
No luck with that either, iirc this is normal with git, unless you push the tag again, my copy will not be updated and stay here forever, unlike branches. No big deal anyway :), I'll remove it from my local copy now.
Comment 7 Dan Winship 2014-05-01 16:16:12 UTC 
*** Bug 727422 has been marked as a duplicate of this bug. ***
Comment 8 Gilles Dartiguelongue 2015-12-30 23:19:40 UTC 
*** Bug 758134 has been marked as a duplicate of this bug. ***
Comment 9 Gilles Dartiguelongue 2015-12-30 23:20:34 UTC 
Could you push this commit please ? I think I lost my write access with the move to git years ago.
Comment 10 Philip Withnall 2017-08-23 09:38:13 UTC 
*** Bug 755928 has been marked as a duplicate of this bug. ***