/bin/sh ./libtool --tag=CC --mode=link x86_64-pc-linux-gnu-gcc -fvisibility=hidden -DUNITDIR=\/var/tmp/portage/dev-libs/ell-0.30/work/ell-0.30/unit/\ -DCERTDIR=\./unit/\ -O2 -pipe -march=native -falign-functions=32:25:16 -fno-common -Werror=format-security -fsigned-char -Wl,-O1 -Wl,--as-needed -Wl,--defsym=__gentoo_check_ldflags__=0 -o unit/test-pbkdf2 unit/test-pbkdf2.o ell/libell-private.la libtool: link: x86_64-pc-linux-gnu-gcc -fvisibility=hidden -DUNITDIR=\/var/tmp/portage/dev-libs/ell-0.30/work/ell-0.30/unit/\ -DCERTDIR=\./unit/\ -O2 -pipe -march=native -falign-functions=32:25:16 -fno-common -Werror=format-security -fsigned-char -Wl,-O1 -Wl,--as-needed -Wl,--defsym=__gentoo_check_ldflags__=0 -o unit/test-pbkdf2 unit/test-pbkdf2.o ell/.libs/libell-private.a ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_gnome_systemd-libressl_test-20200327-211737 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.3.0 * Available Python interpreters, in order of preference: [1] python3.8 [2] python3.7 [3] python3.6 [4] python2.7 (fallback) timestamp of HEAD at this tinderbox image: /var/db/repos/gentoo Sat 28 Mar 2020 05:38:52 AM UTC /var/db/repos/libressl Thu 19 Mar 2020 04:37:24 PM UTC emerge -qpvO dev-libs/ell [ebuild N ] dev-libs/ell-0.30 USE="-glib -pie" ABI_X86="(64) -32 (-x32)"
there is still a similar issue at unstable amd64 tinderbox image 17.1_desktop_gnome_systemd-libressl_test-20200327-211737 (see bug 657352)
Created attachment 626502 [details] emerge-info.txt
Created attachment 626504 [details] dev-libs:ell-0.30:20200328-062242.log
Created attachment 626506 [details] emerge-history.txt
Created attachment 626508 [details] environment
Created attachment 626510 [details] etc.portage.tbz2
Created attachment 626512 [details] logs.tbz2
Created attachment 626514 [details] temp.tbz2
I closed the other bug under the assumption that the test failure was due to a few missing kernel config options but I have added checks and your build.log doesn't show any missing options found. I will look into this again/deeper. Currently I'm unable to reproduce the failure anywhere. Is your tinderbox's current kernel .config available somewhere?
Created attachment 626550 [details] .config kernel config (make default FWIW)
I see now. It's (lack of) CRYPTO_USER_API_HASH which is making this test fail. I'm adding a check for that, and also add a dep on dbus (found out that's required for these tests)
And NOW I can see that we're already testing for this, but only in pkg_pretend so it doesn't show in your build.log. I think I will need the check to happen in pkg_setup as well.
I reworked the ebuild slightly so that the linux-info exported pkg_setup phase handles this by default. The (failed) check should now show up in your build.log. You still cannot pass all tests with your kernel config as-is though.
