22/29 sniffing-test OK 0.12s 23/29 socket-test OK 0.02s 24/29 ssl-test FAIL 0.17s (killed by signal 5 SIGTRAP) 25/29 streaming-test OK 0.07s 26/29 timeout-test OK 8.17s 27/29 tld-test OK 0.01s ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_systemd-libressl_test-20201207-113004 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-10.2.0 * Available Python interpreters, in order of preference: [1] python3.9 [2] python3.8 (fallback) [3] python3.7 (fallback) [4] python2.7 (fallback) Available Rust versions: [1] rust-1.48.0 * The following VMs are available for generation-2: *) AdoptOpenJDK 8.272_p10 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 system-vm The Glorious Glasgow Haskell Compilation System, version 8.8.4 timestamp(s) of HEAD at this tinderbox image: /var/db/repos/gentoo Fri Dec 11 12:35:11 AM UTC 2020 /var/db/repos/libressl Wed Dec 9 02:37:52 PM UTC 2020 emerge -qpvO net-libs/libsoup [ebuild N ] net-libs/libsoup-2.70.0 USE="introspection ssl test vala -brotli -gssapi -gtk-doc -samba" ABI_X86="(64) -32 (-x32)"
Created attachment 677818 [details] emerge-info.txt
Created attachment 677821 [details] emerge-history.txt
Created attachment 677824 [details] environment
Created attachment 677827 [details] etc.portage.tbz2
Created attachment 677830 [details] logs.tbz2
Created attachment 677833 [details] net-libs:libsoup-2.70.0:20201211-015045.log
Created attachment 677836 [details] temp.tbz2
Same with net-libs/libsoup-2.72.0
Known and fixed upstream (for versions >=2.99.1, but patch applies cleanly on libsoup-2.72.0-r1): https://gitlab.gnome.org/GNOME/libsoup/-/commit/af574cf8bebbcb234b05a2919cad53f8d7c8c645
(In reply to Étienne Buira from comment #9) > Known and fixed upstream (for versions >=2.99.1, but patch applies cleanly > on libsoup-2.72.0-r1): > https://gitlab.gnome.org/GNOME/libsoup/-/commit/ > af574cf8bebbcb234b05a2919cad53f8d7c8c645 Thank you! I think this was fixed by upstream commit 70cdb390 in v2.74.0.