Full log written to /var/tmp/portage/sys-apps/systemd-235-r1/work/systemd-235-abi_x86_64.amd64/meson-logs/testlog.txt FAILED: meson-test /usr/bin/python3.4 /usr/lib64/python-exec/python3.4/meson test --no-rebuild --print-errorlogs ninja: build stopped: subcommand failed. * ERROR: sys-apps/systemd-235-r1::gentoo failed (test phase): ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 13.0-systemd_test_20171031-164654 ------------------------------------------------------------------- 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 sys-apps/systemd [ebuild U ] sys-apps/systemd-235-r1 [233-r4] USE="acl gcrypt kmod lz4 pam seccomp ssl -apparmor -audit -build -cryptsetup -curl -elfutils -gnuefi -http -idn -importd -libidn2% -lzma -nat -policykit -qrcode (-selinux) -sysv-utils {-test} -vanilla -xkb (-doc%)" ABI_X86="(64) -32 (-x32)"
Created attachment 501564 [details] emerge-info.txt
Created attachment 501566 [details] emerge-history.txt
Created attachment 501568 [details] environment
Created attachment 501570 [details] etc.portage.tbz2
Created attachment 501572 [details] sys-apps:systemd-235-r1:20171101-034854.log.bz2
Created attachment 501574 [details] temp.tbz2
It looks like it is failing to connect to the system bus. I'm guessing you run this tinderbox in a chroot which does not have access to /var/run/dbus/system_bus_socket on the host. If so, these failures are expected. One way to resolve this would be to use a full container setup with a working dbus system daemon. Otherwise, please skip tests for sys-apps/systemd.
yep, the run file is missing here in a chroot, so systemd is excluded for now till I find a solution : https://github.com/toralf/tinderbox/commit/2ecf39783a05360fc6cbc433af38bd3857c0fedf
