Control: retitle -1 nautilus: FTBFS on arm64:
test-nautilus-search-engine-tracker timed out
(cc'ing Lucas in case whatever heuristics are parsing the log can be
improved)
On Sat, 20 Apr 2024 at 14:09:18 +0200, Lucas Nussbaum wrote:
> Relevant part (hopefully):
> > (tracker-miner-fs-3:3061640): dconf-CRITICAL **: 04:05:03.655: unable to
> > create directory '/sbuild-nonexistent/.cache/dconf': Permission denied.
> > dconf will not work properly.
> >
> > (tracker-miner-fs-3:3061640): libupower-glib-WARNING **: 04:05:03.655:
> > Couldn't connect to proxy: Could not connect: No such file or directory
These are non-fatal (they'd say FATAL-CRITICAL or FATAL-WARNING if they
had been made fatal for testing purposes), although obviously it would
be better to make dconf work correctly (by setting a better $HOME and
$XDG_RUNTIME_DIR, as newer debhelper compat levels do by default) to
reduce the log noise and make real problems visible.
> > 17/17 test-nautilus-search-engine-tracker TIMEOUT 480.24s
> > exit status 1
The failure reason here is that this test timed out.
> > test: test-nautilus-search-engine-tracker
...
> > ERROR: g-io-error-quark: The connection is closed (18)
I think that's more likely to be the root cause. It might be a D-Bus
connection, or some other socket.
smcv
