/gdbus/thread/creation/error: OK /gdbus/thread/sync-call/success: ** ERROR:dbus.c:237:test_sync_call_success: assertion failed (error == NULL): Error spawning command line ?dbus-launch --autolaunch=d12adc5ede6e17857d891d2f59ad1791 --binary-syntax --close-stderr?: Child process exited with code 1 (g-spawn-exit-error-quark, 1) FAIL GTester: last random seed: R02S5e9c6e7b5638072eb36a03e0bbe5502f make[2]: *** [Makefile:927: test-nonrecursive] Terminated ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 13.0-systemd_20170903-225953 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.4.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python3.6 (fallback) [3] python2.7 (fallback) [4] pypy3 (fallback) [5] pypy (fallback) java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.5.1 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv gnome-base/dconf [ebuild N ] gnome-base/dconf-0.26.0-r1 USE="{-test}"
Created attachment 496572 [details] emerge-info.txt
Created attachment 496574 [details] emerge-history.txt
Created attachment 496576 [details] environment
Created attachment 496578 [details] etc.portage.tbz2
Created attachment 496580 [details] gnome-base:dconf-0.26.0-r1:20170926-123139.log
Created attachment 496582 [details] logs.tbz2
Created attachment 496584 [details] temp.tbz2
Created attachment 496586 [details] tests.tbz2
*** Bug 635508 has been marked as a duplicate of this bug. ***
I can reproduce this on amd64-fbsd VM but can't on my main system. What's the state of USE=systemd on sys-apps/dbus?
(In reply to Michał Górny from comment #10) Bad luck, that image is gone 2 :-( I do have only 5 TB for a backlog (splitted into 2 LVs) - and reformatted the inactive LV few days ago for the upcoming switch.
Nevermind, figured it out. The tests are failing if the system-wide instance of D-Bus is not running (i.e. '/etc/init.d/dbus start' fixes them).
which means I have to deactivate test here at the tinderbox for that package ?
Well, you can just start D-Bus, that shouldn't hurt. I'm not sure how to solve this best at package level.