ninja: Entering directory `/var/tmp/portage/dev-libs/appstream-glib-0.7.15/work/appstream-glib-0.7.15-build' ninja: no work to do. 1/2 as-self-test FAIL 0.22 s (killed by signal 5 SIGTRAP) 2/2 asb-self-test OK 0.02 s Ok: 1 ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_hardened-libressl_test-20191129-201951 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.2.0 * llvm: 9.0.0 Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) Available Rust versions: [1] rust-1.39.0 * repository: ==> /var/db/repos/gentoo/metadata/timestamp.chk <== Wed, 04 Dec 2019 10:46:32 +0000 emerge -qpvO dev-libs/appstream-glib [ebuild N ] dev-libs/appstream-glib-0.7.15 USE="introspection -fonts -gtk-doc -stemmer"
Created attachment 598456 [details] emerge-info.txt
Created attachment 598458 [details] dev-libs:appstream-glib-0.7.15:20191204-125841.log
Created attachment 598460 [details] emerge-history.txt
Created attachment 598462 [details] environment
Created attachment 598464 [details] etc.portage.tbz2
Created attachment 598466 [details] logs.tbz2
Created attachment 598468 [details] temp.tbz2
Update summary. [something] is used when something refers to an overlay
Looks like we need to run the test suite in a dbus session.
(In reply to Matt Turner from comment #9) > Looks like we need to run the test suite in a dbus session. The only thing in the test log that looks like an error is > GConf Error: Client failed to connect to the D-BUS daemon: > Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead The code that prints "Using X11 for dbus-daemon autolaunch was disabled at compile time ..." is in dbus and is built iff USE=-X. I thought maybe dbus was somehow auto-launching if USE=X was set, so I tried on a system with dbus built with USE=-X and... the test still passes. Can you reproduce this failure with a more recent version?
not with ~0.8.1