make[1]: Entering directory '/var/tmp/portage/app-backup/burp-2.1.12/work/burp-2.1.12' make[2]: Entering directory '/var/tmp/portage/app-backup/burp-2.1.12/work/burp-2.1.12' FAIL: runner ============================================================================ Testsuite summary for Burp 2.1.12 ============================================================================ ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 13.0-systemd_20170903-225953 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.4.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python3.6 (fallback) [3] python2.7 (fallback) [4] pypy3 (fallback) [5] pypy (fallback) java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.5.1 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv app-backup/burp [ebuild N ] app-backup/burp-2.1.12 USE="acl ipv6 xattr -libressl {-test}"
Created attachment 496688 [details] emerge-info.txt
Created attachment 496690 [details] app-backup:burp-2.1.12:20170927-055834.log
Created attachment 496692 [details] emerge-history.txt
Created attachment 496694 [details] environment
Created attachment 496696 [details] etc.portage.tbz2
Created attachment 496698 [details] logs.tbz2
Created attachment 496700 [details] temp.tbz2
The affected version has just been removed, hopefully the problem is no longer present in 2.1.20 (at least on my system, all tests succeed).