Hello, On FreeBSD 10, 9.3, 8.4 (running inside kvm), the test "test-lock" sometime gets stuck.
It was found through libunistring but I've also reproduced it with the latest
gnulib directly (v0.1-210-g4738e5a), by doing:
./gnulib/gnulib-tool --create-testdir --dir=test-thread --with-tests thread
cd test-thread
./configure && make dist
Then running the tarball test package inside the FreeBSD virtual machines.
A comment by Daiki Ueno indicates this might already be known issue:
http://lists.gnu.org/archive/html/bug-libunistring/2014-09/msg00005.html
This is failure is somewhat reproducible.
On some occasions the test executable is running at %100 CPU for a long time:
PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND
24972 gordon 11 44 0 12616K 4372K urdlck 10:30 98.97% test-lock
In other cases it completes successfully after ~2 minutes.
Attached are logs from Valgrind/Helgrind tool.
On Ubuntu, it only complains about access to a global "volative int" variable,
which I guess is intentional.
On FreeBSD, there are many more complains about other issues (not sure if
false-positives or not).
Regards,
- Assaf
Ubuntu.test-lock.helgrind.log.xz
Description: application/xz
FreeBSD10.test-lock.helgrind.log.xz
Description: application/xz
