>>> Test phase: sys-devel/llvm-9999 * abi_x86_32.x86: running multilib-minimal_abi_src_test >>> Working in BUILD_DIR: "/var/tmp/portage/sys-devel/llvm-9999/work/llvm-9999-abi_x86_32.x86" ninja -j12 -v check [0/1] cd /var/tmp/portage/sys-devel/llvm-9999/work/llvm-9999-abi_x86_32.x86/test && /usr/bin/lit -sv --param llvm_site_config=/var/tmp/portage/sys-devel/llvm-9999/work/llvm-9999-abi_x86_32.x86/test/lit.site.cfg --param llvm_unit_site_config=/var/tmp/portage/sys-devel/llvm-9999/work/llvm-9999-abi_x86_32.x86/test/Unit/lit.site.cfg /var/tmp/portage/sys-devel/llvm-9999/work/llvm-9999-abi_x86_32.x86/test lit: discovery.py:190: warning: test suite 'LLVM-Unit' contained no tests -- Testing: 16424 tests, 2 threads -- For comparison, a local run discovers over 18.5k tests, so I suspect something's broken. However, I need to check on abi_x86_64 when I have more time ;-).
Yep, same results for the native ABI. However, it seems that the unit tests are built...
Seems to affect clang as well.
This has been a result of bad rpath and it has been fixed upstream.