mirror of
https://github.com/bitcoin/bitcoin.git
synced 2025-01-10 11:57:28 -03:00
56aad83307
This should be long enough (with headroom) for our longest running tests, which even under MSAN, TSAN, Valgrind, etc max out at about 800s. i.e under Valgrind I see the longer runtimes as: ```bash 135/136 Test #8: bench_sanity_check_high_priority ..... Passed 371.19 sec 136/136 Test #122: coinselector_tests ................... Passed 343.39 sec ``` In the CI `tests` under TSAN: ```bash tests ................................ Passed 795.20 sec ``` and MSAN: ```bash tests ................................ Passed 658.48 sec ``` This will also prevent the current issue we are seeing of `ctest` running until it reaches the CI timeout, see #30969. However, we still need to figure out what underlying issue is causing the tests to (sometimes) run for so long, but in the mean time, this will stop `ctest` wasting our CI CPU. |
||
---|---|---|
.. | ||
00_setup_env.sh | ||
00_setup_env_arm.sh | ||
00_setup_env_i686_centos.sh | ||
00_setup_env_i686_multiprocess.sh | ||
00_setup_env_mac_cross.sh | ||
00_setup_env_mac_native.sh | ||
00_setup_env_native_asan.sh | ||
00_setup_env_native_fuzz.sh | ||
00_setup_env_native_fuzz_with_msan.sh | ||
00_setup_env_native_fuzz_with_valgrind.sh | ||
00_setup_env_native_msan.sh | ||
00_setup_env_native_nowallet_libbitcoinkernel.sh | ||
00_setup_env_native_previous_releases.sh | ||
00_setup_env_native_tidy.sh | ||
00_setup_env_native_tsan.sh | ||
00_setup_env_native_valgrind.sh | ||
00_setup_env_s390x.sh | ||
00_setup_env_win64.sh | ||
01_base_install.sh | ||
02_run_container.sh | ||
03_test_script.sh | ||
GetCMakeLogFiles.cmake | ||
wrap-valgrind.sh | ||
wrap-wine.sh |