PASS: ssl-test 11 /ssl/strictness/sync/non-strict/with-ca PASS: ssl-test 12 /ssl/strictness/sync/non-strict/without-ca ERROR: ssl-test - exited with status 1 PASS: streaming-test 1 /streaming/chunked PASS: streaming-test 2 /streaming/content-length PASS: streaming-test 3 /streaming/eof ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop-plasma-systemd_test_20190328-000152 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-8.3.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) [3] pypy3 (fallback) java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.10.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpvO net-libs/libsoup [ebuild N ] net-libs/libsoup-2.64.2 USE="introspection ssl test vala -debug -gssapi -samba" ABI_X86="(64) -32 (-x32)"
Created attachment 571256 [details] emerge-info.txt
Created attachment 571258 [details] emerge-history.txt
Created attachment 571260 [details] environment
Created attachment 571262 [details] etc.portage.tbz2
Created attachment 571264 [details] logs.tbz2
Created attachment 571266 [details] net-libs:libsoup-2.64.2:20190330-164350.log
Created attachment 571268 [details] temp.tbz2
I'm seeing this as well. The actual failing sub-test is a few lines earlier: FAIL: ssl-test 2 /ssl/tls-interaction My system: Portage 2.3.62 (python 3.6.5-final-0, hardened/linux/musl/amd64, gcc-8.3.0, musl-9999, 4.20.0 x86_64) ================================================================= System uname: Linux-4.20.0-x86_64-Intel-R-_Xeon-R-_CPU_X5675_@_3.07GHz-with-gentoo-2.6 KiB Mem: 74279532 total, 25782548 free KiB Swap: 28819452 total, 28805116 free sh bash 4.4_p23-r1 ld GNU ld (Gentoo 2.31.1 p7) 2.31.1 app-shells/bash: 4.4_p23-r1::gentoo dev-java/java-config: 2.2.0-r4::gentoo dev-lang/perl: 5.26.2::gentoo dev-lang/python: 2.7.15::gentoo, 3.6.5::gentoo dev-util/cmake: 3.9.6::gentoo sys-apps/baselayout: 2.6-r1::gentoo sys-apps/sandbox: 2.13::musl sys-devel/autoconf: 2.13-r1::gentoo, 2.69-r4::gentoo sys-devel/automake: 1.11.6-r3::gentoo, 1.16.1-r1::gentoo sys-devel/binutils: 2.31.1-r6::gentoo sys-devel/gcc: 8.3.0-r1::musl sys-devel/gcc-config: 2.0::gentoo sys-devel/libtool: 2.4.6-r3::gentoo sys-devel/make: 4.2.1-r4::gentoo sys-kernel/linux-headers: 4.20::musl (virtual/os-headers) sys-libs/musl: 9999::gentoo
This is https://gitlab.gnome.org/GNOME/glib-networking/issues/70 It needs a bump to net-libs/glib-networking or the linked commit applied. With that patch to glib-networking, the libsoup test suite passes.
Same failure on ia64 with =net-libs/glib-networking-2.60.3.
(In reply to Émeric Maschino from comment #10) > Same failure on ia64 with =net-libs/glib-networking-2.60.3. But upgrading to =net-libs/libsoup-2.66.4 did the trick for me on ia64.