Created attachment 378014 [details] build log On my hardened ~amd64 machine I see the following test failure for dconf. TEST: gdbus-thread... (pid=15527) /gdbus/thread/creation/error: OK /gdbus/thread/sync-call/success: ** ERROR:dbus.c:237:test_sync_call_success: assertion failed (error == NULL): The connection is closed (g-io-error-quark, 18) FAIL GTester: last random seed: R02S425ea1729d0dc8633550e6be1363a789 /bin/sh: line 1: 5851 Terminated G_DEBUG=gc-friendly MALLOC_CHECK_=2 MALLOC_PERTURB_=$((${RANDOM:-256} % 256)) gtester --verbose paths changeset shm gvdb gdbus-thread gdbus-filter libdbus-1 engine client Makefile:985: recipe for target 'test-nonrecursive' failed
Created attachment 378016 [details] emerge --info
I cannot produce this, not sure if could be due hardened. Are you able to run tests when manually compiling outside portage?
I took a closer look and could find no hardened related errors in the system logs, which of course doesn't mean, that it's not hardened related (oh no, double negative). Running 'ebuild <dconf> compile' and 'make check' in a root-terminal gives me the same error as in the build log.
(In reply to Pacho Ramos from comment #2) > I cannot produce this, not sure if could be due hardened. Are you able to > run tests when manually compiling outside portage? Not due to hardened, happens to me on not-hardened. I presume it fails because dbus isn't running?
Maybe "unset DBUS_SESSION_BUS_ADDRESS" before running tests could help. Other option is to run something like "dbus-launch Xemake check"
(In reply to Pacho Ramos from comment #5) > Maybe "unset DBUS_SESSION_BUS_ADDRESS" before running tests could help. > Other option is to run something like "dbus-launch Xemake check" The first one works fine. Please add it to the ebuild, thanks.
(For dconf-0.22.0, of course)
Maybe we should finally add this to the eclass -> bug 515196 As this is appearing every day on random ebuilds constantly :S
(In reply to Pacho Ramos from comment #8) > Maybe we should finally add this to the eclass -> bug 515196 > > As this is appearing every day on random ebuilds constantly :S Ok. This is now fixed, please close.
