[Pkg-utopia-maintainers] Bug#897607: dbus: Please raise timeout for a few test cases (or disable) in riscv64

Simon McVittie smcv at debian.org
Fri May 11 09:23:35 BST 2018


On Fri, 11 May 2018 at 09:55:38 +0200, Manuel A. Fernandez Montecelo wrote:
> 2018-05-11 2:06 GMT+02:00 Manuel A. Fernandez Montecelo
> <manuel.montezelo at gmail.com>:
> >
> > It's starting to build now in one if the buildds, I hope that tomorrow
> > we have the answer.
> 
> It failed, log attached.  This is the bit that failed:
> 
> ==> debian/build-debug/test/test-refs.log <==
> test-refs: pthread_mutex_lock.c:115: __pthread_mutex_lock: Assertion
> `mutex->__data.__owner == 0' failed.
> ../../../build-aux/tap-driver.sh: line 639: 11060 Aborted                 "$@"
> # random seed: R02S40f93f7456852a624ddb781e5293fa4c
> 1..4
> # Start of refs tests
> # Resetting test timeout (reference: 0x2aaaac80c0; factor: 1)
> ERROR: test-refs - too few tests run (expected 4, got 0)
> ERROR: test-refs - exited with status 134 (terminated by signal 6?)

That seems to be a legitimate test failure (a glibc bug, not a
timeout). Are atomic operations and mutexes believed to work correctly
in qemu-system-riscv64?

Thanks,
    smcv



More information about the Pkg-utopia-maintainers mailing list