Ran 4 tests Passed 0 tests Failed 4 tests Error in 0 tests Skipped 0 tests * ERROR: dev-libs/libusb-1.0.21::gentoo failed (test phase): ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-no-multilib_libressl-test_20171022-133742 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.4.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 (fallback) emerge -qpv dev-libs/libusb [ebuild N ] dev-libs/libusb-1.0.21 USE="-debug -doc -examples -static-libs {-test} -udev"
Created attachment 499896 [details] emerge-info.txt
Created attachment 499898 [details] dev-libs:libusb-1.0.21:20171024-041352.log
Created attachment 499900 [details] emerge-history.txt
Created attachment 499902 [details] environment
Created attachment 499904 [details] etc.portage.tbz2
Created attachment 499906 [details] logs.tbz2
Created attachment 499908 [details] temp.tbz2
Created attachment 499910 [details] tests.tbz2
(In reply to Toralf Förster from comment #0) > Failed 4 tests The tests fail because they depend on external hardware and/or at the very least a particular kernel configurations/udev environment. The tests are poor and it would make sense to simply ignore them.