Full log written to /var/tmp/portage/net-irc/hexchat-2.14.1/work/hexchat-2.14.1-build/meson-logs/testlog.txt FAILED: meson-test /usr/bin/python3.5 -u /usr/lib/python-exec/python3.5/meson test --no-rebuild --print-errorlogs ninja: build stopped: subcommand failed. * ERROR: net-irc/hexchat-2.14.1::gentoo failed (test phase): ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop-gnome_test_20180508-174739 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python2.7 (fallback) [3] pypy3 (fallback) [4] pypy (fallback) java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.7.0 [icedtea-bin-8] 2) JamVM JDK 2.0.0 [jamvm] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm [2] jamvm emerge -qpv net-irc/hexchat [ebuild N ] net-irc/hexchat-2.14.1 USE="dbus gtk libnotify python ssl -debug -libcanberra -libproxy -libressl -lua -perl -plugin-checksum -plugin-fishlim -plugin-sysinfo (-theme-manager)" PYTHON_SINGLE_TARGET="python3_5 -python3_4 -python3_6" PYTHON_TARGETS="python3_5 -python3_4 -python3_6"
Created attachment 531436 [details] emerge-info.txt
Created attachment 531438 [details] emerge-history.txt
Created attachment 531440 [details] environment
Created attachment 531442 [details] etc.portage.tbz2
Created attachment 531444 [details] logs.tbz2
Created attachment 531446 [details] net-irc:hexchat-2.14.1:20180514-202712.log
Created attachment 531448 [details] temp.tbz2
Update summary. [something] is used when something refers to an overlay
I am unable to reproduce this on my local machine. The issue seems that the tinderbox was unable to find a given URL, so I've tested with FEATURES=network-sandbox explicitly set. Still, I can't reproduce this. Since this bug is now over four years old and Hexchat has meanwhile received two minor version bumps, shouldn't we just close the bug? To me it seems like a newer version (either of the software or of the ebuild) must have fixed the issue.
Sure.
