Your message dated Mon, 23 Oct 2017 15:01:26 +0100
with message-id <[email protected]>
and subject line Re: Bug#873823: dbus: FTBFS on sparc64: test-dbus-daemon:
FATAL-ERROR: timed out
has caused the Debian Bug report #873823,
regarding dbus: FTBFS on sparc64: test-dbus-daemon: FATAL-ERROR: timed out
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
873823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873823
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: dbus
Version: 1.11.16+really1.11.16-2
Severity: normal
I recently enabled build-time tests for dbus, having first fixed the
home directory issue that made them fail on all buildds. They pass on
most Linux architectures, but fail on sparc64.
https://buildd.debian.org/status/fetch.php?pkg=dbus&arch=sparc64&ver=1.11.16%2Breally1.11.16-2&stamp=1501416799&raw=0
> **
> (/<<BUILDDIR>>/dbus-1.11.16+really1.11.16/debian/build-debug/test/.libs/test-dbus-daemon:7617):
> ERROR **: timed out
This test times out after 60 seconds:
> /* Prevent tests from hanging forever. This is intended to be long enough
> * that any reasonable regression test on any reasonable hardware would
> * have finished. */
> #define TIMEOUT 60
— test/test-utils-glib.c
I think the timeout is during the /echo/limited test-case, which severely
cuts down the number of messages that the dbus-daemon is willing to keep
in-flight at a time, cutting throughput from 250 to 200 messages per
second. This seems really slow: on my 5 year old x86-64 laptop I get
more than 20 times that throughput.
If sparc64 is really that slow, it's just an arbitrary timeout and could
be increased (the only purpose is to make each test take a finite time
to fail if something gets wedged). Is it?
(X-Debbugs-Cc to debian-sparc)
S
--- End Message ---
--- Begin Message ---
Version: 1.11.20-1
On Thu, 31 Aug 2017 at 15:09:31 +0100, Simon McVittie wrote:
> https://buildd.debian.org/status/fetch.php?pkg=dbus&arch=sparc64&ver=1.11.16%2Breally1.11.16-2&stamp=1501416799&raw=0
> > **
> > (/<<BUILDDIR>>/dbus-1.11.16+really1.11.16/debian/build-debug/test/.libs/test-dbus-daemon:7617):
> > ERROR **: timed out
...
> If sparc64 is really that slow, it's just an arbitrary timeout and could
> be increased
Blindly increasing the timeout seems to have worked.
https://bugs.freedesktop.org/show_bug.cgi?id=103009
https://cgit.freedesktop.org/dbus/dbus/commit/?id=3d557ff7b155d1e0f1cdbfd82cff0ac7ed1b7c4b
Regards,
smcv
--- End Message ---
_______________________________________________
Pkg-utopia-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
