2018-05-11 10:23 GMT+02:00 Simon McVittie <s...@debian.org>: > 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.montez...@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?
Yep, it should work fine, CC'ing Aurélien so it's under his radar. It works fine in hardware too, just compiled successfully, see attached log. So I guess that it's fine and done from the packaging side, unless you want to tweak the timeouts further. Thanks! -- Manuel A. Fernandez Montecelo <manuel.montez...@gmail.com>
dbus_1.13.4-2_riscv64-2018-05-11T08:00:07Z.build.xz
Description: application/xz