ldas-tools-framecpp 2.9.2 and later: timeout too short for test_Checksum on arm64 Debian

Attempting to build for Debian Bookworm -

The timeouts set for the Checksum test seem to be too short for this particular system (Cavium ThunderX). I didn't attempt to run it on a RasPi3B. https://hypatia.aei.mpg.de/lsc-arm64-bookworm/ldas-tools-framecpp_2.9.2-1+deb12u0_arm64.--pbuilderlog:

25: [1;34;49mEntering test module "Master Test Suite"
25: [0;39;49m[1;34;49m./test/test_CheckSum.cc(100): Entering test case "test_checksum_constructor"
25: [0;39;49m./test/test_CheckSum.cc(106): [1;32;49minfo: check test_checksum.value( ) == expected_value has passed[0;39;49m
25: [1;34;49m./test/test_CheckSum.cc(100): Leaving test case "test_checksum_constructor"; testing time: 1456us
25: [0;39;49m[1;34;49m./test/test_CheckSum.cc(110): Entering test case "test_checksum_zero_bytes"
25: [0;39;49m./test/test_CheckSum.cc(117): [1;32;49minfo: check test_cksum.checksum( ) == expected_value has passed[0;39;49m
25: ./test/test_CheckSum.cc(118): [1;32;49minfo: check test_checksum.value( ) == expected_value has passed[0;39;49m
25: [1;34;49m./test/test_CheckSum.cc(110): Leaving test case "test_checksum_zero_bytes"; testing time: 1231us
25: [0;39;49m[1;34;49m./test/test_CheckSum.cc(121): Entering test case "test_checksum_4096_bytes"
25: [0;39;49m./test/test_CheckSum.cc(137): [1;32;49minfo: check test_cksum.checksum( ) == expected_value has passed[0;39;49m
25: ./test/test_CheckSum.cc(138): [1;32;49minfo: check test_checksum.value( ) == expected_value has passed[0;39;49m
25: [1;34;49m./test/test_CheckSum.cc(121): Leaving test case "test_checksum_4096_bytes"; testing time: 1336us
25: [0;39;49m[1;34;49m./test/test_CheckSum.cc(141): Entering test case "test_checksum_4096_bytes_2_stages"
25: [0;39;49m./test/test_CheckSum.cc(166): [1;32;49minfo: check test_cksum.checksum( ) == expected_value has passed[0;39;49m
25: ./test/test_CheckSum.cc(167): [1;32;49minfo: check test_checksum->value( ) == expected_value has passed[0;39;49m
25: [1;34;49m./test/test_CheckSum.cc(141): Leaving test case "test_checksum_4096_bytes_2_stages"; testing time: 1345us
25: [0;39;49m[1;34;49m./test/test_CheckSum.cc(170): Entering test case "test_checksum_4096_bytes_reset"
25: [0;39;49m./test/test_CheckSum.cc(195): [1;32;49minfo: check test_cksum.checksum( ) == expected_value has passed[0;39;49m
25: ./test/test_CheckSum.cc(196): [1;32;49minfo: check test_checksum.value( ) == expected_value has passed[0;39;49m
25: ./test/test_CheckSum.cc(212): [1;32;49minfo: check test_cksum.checksum( ) == expected_value_ramped_4096 has passed[0;39;49m
25: ./test/test_CheckSum.cc(213): [1;32;49minfo: check test_checksum.value( ) == expected_value_ramped_4096 has passed[0;39;49m
25: [1;34;49m./test/test_CheckSum.cc(170): Leaving test case "test_checksum_4096_bytes_reset"; testing time: 1977us
25: [0;39;49m[1;34;49m./test/test_CheckSum.cc(216): Entering test case "test_checksum_4096_bytes_no_extend"
25: [0;39;49m./test/test_CheckSum.cc(232): [1;32;49minfo: check test_cksum.checksum( ) == expected_value has passed[0;39;49m
25: ./test/test_CheckSum.cc(233): [1;32;49minfo: check test_checksum.value( ) == expected_value has passed[0;39;49m
25: ./test/test_CheckSum.cc(241): [1;32;49minfo: check test_cksum.checksum( ) == expected_value has passed[0;39;49m
25: ./test/test_CheckSum.cc(242): [1;32;49minfo: check test_checksum.value( ) == expected_value has passed[0;39;49m
25: [1;34;49m./test/test_CheckSum.cc(216): Leaving test case "test_checksum_4096_bytes_no_extend"; testing time: 1441us
25: [0;39;49m[1;34;49m./test/test_CheckSum.cc(245): Entering test case "test_checksum_8589934592_bytes"

then, with other tests interleaved,

25: [0;39;49m./test/test_CheckSum.cc(271): [1;32;49minfo: check test_cksum_boost.checksum( ) == expected_value has passed[0;39;49m
25: ./test/test_CheckSum.cc(272): [1;32;49minfo: check test_cksum_ldas.checksum( ) == expected_value has passed[0;39;49m
25: ./test/test_CheckSum.cc(273): [1;32;49minfo: check test_checksum.value( ) == expected_value has passed[0;39;49m
25: ./test/test_CheckSum.cc(275): [1;33;49mwarning: in "test_checksum_8589934592_bytes": Time to execute cksum_boost calculation: 34 seconds [Upper limit: 15 seconds ][0;39;49m
25: ./test/test_CheckSum.cc(279): [1;31;49merror: in "test_checksum_8589934592_bytes": Time to execute cksum_ldas calculation: 15 seconds [Upper limit: 15 seconds ][0;39;49m
25: ./test/test_CheckSum.cc(283): [1;31;49merror: in "test_checksum_8589934592_bytes": Time to execute CheckSumCRC calculation: 15 seconds [Upper limit: 15 seconds ][0;39;49m
25: [1;34;49m./test/test_CheckSum.cc(245): Leaving test case "test_checksum_8589934592_bytes"; testing time: 66675066us
25: [0;39;49m[1;34;49mLeaving test module "Master Test Suite"; testing time: 66684313us
25: [0;39;49m
25: [1;31;49m*** 2 failures are detected in the test module "Master Test Suite"
25: [0;39;49m
36/38 Test #25: test_CheckSum ....................***Failed   66.72 sec

The host system is Debian Buster. The boost version in use is 1.74

Since this isn't a precision test, and actual runtimes on a production system may wildly differ from those seen on the build machine, I'm leaning towards ignoring the test result - it's the only failure (although above "2 failures are detected" - apparently only the "error"s are counted?):

97% tests passed, 1 tests failed out of 38

@ed-maros may I have your advice?