Test error on btree - random concurrent inserts

I've stepped through the build steps with COMPILER=gcc, as enumerated in the README. Running the tests results in this error, which I've reproduced several times.

Command:
make run-tests

Output:

Checking for mismatched config...No mismatched config found
BINDIR=build/bin ./test.sh
test.sh: build_dir='build', BINDIR='build/bin'
test.sh: Tue 29 Aug 2023 10:10:21 PM PDT Start SplinterDB Test Suite Execution.
+ SEED=135
+ run_type=' '
+ '[' false == true ']'
+ set +x

+ build/bin/unit_test
argv[i]=build/bin/unit_test
Running 7 CTests, suite name 'all', test case 'all'.
TEST 1/37 splinterdb_quick:test_basic_flow [OK]
TEST 2/37 splinterdb_quick:test_apis_for_max_key_length [OK]
TEST 3/37 splinterdb_quick:test_key_size_gt_max_key_size [OK]
TEST 4/37 splinterdb_quick:test_value_size_gt_max_value_size [OK]
TEST 5/37 splinterdb_quick:test_variable_length_values [OK]
TEST 6/37 splinterdb_quick:test_basic_iterator [OK]
TEST 7/37 splinterdb_quick:test_splinterdb_iterator_with_startkey [OK]
TEST 8/37 splinterdb_quick:test_splinterdb_iterator_with_non_existent_startkey [OK]
TEST 9/37 splinterdb_quick:test_splinterdb_iterator_with_missing_startkey_in_sequence [OK]
TEST 10/37 splinterdb_quick:test_close_and_reopen [OK]
TEST 11/37 splinterdb_quick:test_repeated_insert_close_reopen [OK]
TEST 12/37 splinterdb_quick:test_custom_data_config [OK]
TEST 13/37 splinterdb_quick:test_iterator_custom_comparator [OK]
TEST 14/37 misc:test_assert_basic_msg [OK]
TEST 15/37 misc:test_assert_msg_with_args [OK]
TEST 16/37 misc:test_ctest_assert_prints_user_msg_with_params [OK]
TEST 17/37 btree_stress:test_random_inserts_concurrent ./test.sh: line 98: 2873116 Aborted                 (core dumped) "$@"
make: *** [Makefile:421: run-tests] Error 134

Run make run-tests with the reported GCC configuration and focus on btree_stress:test_random_inserts_concurrent, which aborts during build/bin/unit_test. Start with the test output and the test.sh invocation at line 98; done means identifying and fixing the cause of the abort, then completing the test suite successfully.