misc: setarch: [03] uname26-version ... OK libsmartcols: fromfile: [11] wrap ... OK libmount: tab files-py ... FAILED (1 from 11 sub-tests) misc: setarch ... OK (all 3 sub-tests PASSED) misc: strtosize ... OK blkid: superblocks probing: [33] minix-LE ... OK ------------------------------------------------------------------- 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 * llvm-config: 3.9.1 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: 1) IcedTea JDK 7.2.6.11 [icedtea-bin-7] *) IcedTea JDK 3.5.1 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-7 [2] icedtea-bin-8 system-vm emerge -qpv sys-apps/util-linux [ebuild U ] sys-apps/util-linux-2.30.2 [2.30.1] USE="cramfs ncurses nls pam python readline suid udev unicode -build -caps -fdformat -kill (-selinux) -slang -static-libs -systemd {-test} -tty-helpers" ABI_X86="(64) -32 (-x32)" PYTHON_SINGLE_TARGET="python3_4 -python2_7 -python3_5 -python3_6" PYTHON_TARGETS="python2_7 python3_4 -python3_5 -python3_6"
Created attachment 497658 [details] emerge-info.txt
Created attachment 497660 [details] emerge-history.txt
Created attachment 497662 [details] environment
Created attachment 497664 [details] etc.portage.tbz2
Created attachment 497666 [details] logs.tbz2
Created attachment 497668 [details] sys-apps:util-linux-2.30.2:20171004-022210.log
Created attachment 497670 [details] temp.tbz2
Created attachment 497672 [details] tests.tbz2
Same test fails on ppc: libmount: tab files-py: [10] find-target3 ... OK libmount: tab files-py: [11] find-pair ... OK libsmartcols: fromfile: [01] tree ... OK libmount: tab files-py ... FAILED (1 from 11 sub-tests)
Can reproduce with util-linux-2.30.2[python], still reproducible with current git master.
Same as 624132.
*** This bug has been marked as a duplicate of bug 624132 ***