aboutsummaryrefslogtreecommitdiff
path: root/ci/test/06_script_b.sh
diff options
context:
space:
mode:
authorfanquake <fanquake@gmail.com>2023-05-17 10:53:47 +0100
committerfanquake <fanquake@gmail.com>2023-05-17 10:57:39 +0100
commit6a936580d1c42576f627d5fac5423ec7af88e547 (patch)
treea2b954353f599e130c3ccae6337de912f7d1754f /ci/test/06_script_b.sh
parenta75c77ea903c100531e0fc5fde94bb9b52642145 (diff)
downloadbitcoin-6a936580d1c42576f627d5fac5423ec7af88e547.tar.xz
ci: remove RUN_SECURITY_TESTS
We no-longer run any security/syymbol checks in the CI, and doubt we will in future (if we do, it'll be via Guix, where this var would be redundant in any case). The CI environment doesn't (exactly) match the release build environment (and is semi-regularly changing), and the binaries produced in the CI don't match how we build release binaries, so there is no point trying to run these checks, especially as we add more involved tests, i.e #26953.
Diffstat (limited to 'ci/test/06_script_b.sh')
-rwxr-xr-xci/test/06_script_b.sh4
1 files changed, 0 insertions, 4 deletions
diff --git a/ci/test/06_script_b.sh b/ci/test/06_script_b.sh
index 075685ee8d..d8fab1cc45 100755
--- a/ci/test/06_script_b.sh
+++ b/ci/test/06_script_b.sh
@@ -210,10 +210,6 @@ if [ "${RUN_TIDY}" = "true" ]; then
git --no-pager diff
fi
-if [ "$RUN_SECURITY_TESTS" = "true" ]; then
- make test-security-check
-fi
-
if [ "$RUN_FUZZ_TESTS" = "true" ]; then
bash -c "LD_LIBRARY_PATH=${DEPENDS_DIR}/${HOST}/lib test/fuzz/test_runner.py ${FUZZ_TESTS_CONFIG} $MAKEJOBS -l DEBUG ${DIR_FUZZ_IN}"
fi