make[1]: Entering directory '/var/tmp/portage/app-backup/burp-2.3.38/work/burp-2.3.38' make[2]: Entering directory '/var/tmp/portage/app-backup/burp-2.3.38/work/burp-2.3.38' FAIL: runner ============================================================================ Testsuite summary for Burp 2.3.38 ============================================================================ ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_hardened-libressl_abi32+64_test-20201027-192603 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-8.3.1 [3] x86_64-pc-linux-gnu-10.2.0 * clang version 11.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/11/bin /usr/lib/llvm/11 11.0.0 Available Python interpreters, in order of preference: [1] python3.7 [2] python3.9 (fallback) [3] python3.8 (fallback) [4] python2.7 (fallback) [5] pypy3 (fallback) Available Rust versions: [1] rust-bin-1.47.0 * [2] rust-1.47.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 Tue Nov 10 04:05:36 PM UTC 2020 /var/db/repos/libressl Sat Nov 7 03:06:11 PM UTC 2020 emerge -qpvO app-backup/burp [ebuild U ] app-backup/burp-2.3.38 [2.3.36] USE="acl ipv6 libressl test xattr"
this seems to be either still an issue or a similarity to the one reported in bug 641926
Created attachment 670748 [details] emerge-info.txt
Created attachment 670751 [details] app-backup:burp-2.3.38:20201110-161124.log
Created attachment 670754 [details] emerge-history.txt
Created attachment 670757 [details] environment
Created attachment 670760 [details] etc.portage.tbz2
Created attachment 670763 [details] logs.tbz2
Created attachment 670766 [details] temp.tbz2
*** This bug has been marked as a duplicate of bug 753707 ***