I had to kill the test case after 7 hours of inactivity make[4]: Entering directory '/var/tmp/portage/app-i18n/ibus-1.5.16/work/ibus-1.5.16/src/tests' make[5]: Entering directory '/var/tmp/portage/app-i18n/ibus-1.5.16/work/ibus-1.5.16/src/tests' FAIL: ibus-bus PASS: ibus-config PASS: ibus-configservice PASS: ibus-factory ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 13.0-desktop_libressl_20170918-162903 ------------------------------------------------------------------- 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) 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-i18n/ibus [ebuild N ] app-i18n/ibus-1.5.16 USE="X emoji gtk gtk2 introspection libnotify nls python -gconf -kde {-test} -vala -wayland" PYTHON_TARGETS="python2_7 python3_4 -python3_5 -python3_6"
Created attachment 495738 [details] emerge-info.txt
Created attachment 495740 [details] app-i18n:ibus-1.5.16:20170921-000629.log
Created attachment 495742 [details] emerge-history.txt
Created attachment 495744 [details] environment
Created attachment 495746 [details] etc.portage.tbz2
Created attachment 495748 [details] logs.tbz2
Created attachment 495750 [details] temp.tbz2
It seems that some tests are flaky