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 719517 - libsoup-2.42.3.1 fails tests on Gentoo
libsoup-2.42.3.1 fails tests on Gentoo
Status: RESOLVED FIXED
Product: libsoup
Classification: Core
Component: Misc
2.42.x
Other Linux
: Normal normal
: ---
Assigned To: libsoup-maint@gnome.bugs
libsoup-maint@gnome.bugs
Depends on:
Blocks:
 
 
Reported: 2013-11-28 21:22 UTC by Markus Oehme
Modified: 2013-11-30 20:51 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
build log (139.94 KB, text/plain)
2013-11-28 21:22 UTC, Markus Oehme
Details
test suite log (5.27 KB, text/plain)
2013-11-28 21:26 UTC, Markus Oehme
Details

Description Markus Oehme 2013-11-28 21:22:25 UTC
Created attachment 263080 [details]
build log

I'm seeing test failures for libsoup on Gentoo unstable on the hardened amd64 platform. The failing test are cache-test, ntlm-test, session-test, requester-test.

Please state what information is necessary to debug this.
Comment 1 Markus Oehme 2013-11-28 21:26:26 UTC
Created attachment 263081 [details]
test suite log

This is the log that the test suite produces. HTH.
Comment 2 Markus Oehme 2013-11-29 12:40:10 UTC
The corresponding Gentoo bug is [1] and it turns out, that 3 of the 4 test failures were packaging issues. The still failing test is cache-test.

[1] https://bugs.gentoo.org/show_bug.cgi?id=413233
Comment 3 Dan Winship 2013-11-30 20:48:18 UTC
(In reply to comment #2)
> The corresponding Gentoo bug is [1] and it turns out, that 3 of the 4 test
> failures were packaging issues.

No, it's a libsoup bug; the tests should not be pulling in any D-Bus-based giomodules.

> The still failing test is cache-test.

The attached test-suite.log does not show a cache-test failure... meaning probably that that was from a different run, and it failed one time but not the other. Meaning it was probably bug 698305, and you can apply https://git.gnome.org/browse/libsoup/commit/?id=164e49a2 to fix it.
Comment 4 Dan Winship 2013-11-30 20:51:34 UTC
oh, actually, that's already fixed as well:
https://git.gnome.org/browse/libsoup/commit/?id=a5d3351c