bricks.test sporadic failure
I'm installing a new Ryzen7-based laptop with Debian unstable, and observed a failure of bricks.test
next ~git/spot/tests % cat core/bricks.test.log
+ . ./defs
+ test -f ./defs
+ test -z .
+ test -f ./../core/defs.in
+ echo == Running test bricks.test
== Running test bricks.test
+ echo bricks.test
+ sed -e s,.*[\/],,;s/\.test$//
+ me=bricks
+ testSubDir=bricks.dir
+ chmod -R a+rwx bricks.dir
+ rm -rf bricks.dir
+ mkdir bricks.dir
+ cd bricks.dir
+ srcdir=../.
+ DOT=dot
+ LBTT=lbtt
+ LBTT_TRANSLATE=lbtt-translate
+ VALGRIND=valgrind
+ SPIN=spin
+ LTL2BA=ltl2ba
+ PYTHON=/usr/bin/python3
+ top_srcdir=/home/adl/git/spot
+ unset SPOT_DOTEXTRA
+ unset SPOT_DOTDEFAULT
+ set -x
+ set -e
+ seq 0 1999
+ ../bricks
terminate called after throwing an instance of 'brick::_assert::AssertFailed'
what(): .../spot/bricks/brick-hashset: 821:
expected it < end
Aborted
FAIL core/bricks.test (exit status: 134)
Unfortunately, running the test three additional times succeeded. I suspect this depends on the ordering of thread operations. The failure occurred during a make -j16 check
run.