mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 14:48:21 +00:00
ci: Remove ZEEK_CI_DISABLE_SCRIPT_PROFILING logic
To my knowledge this doesn't make a huge difference anymore and locally
I'm only using ASAN builds. It's not actually too slow.
(cherry picked from commit 344369f169
)
This commit is contained in:
parent
2ceae52bfa
commit
5e383ad13e
2 changed files with 0 additions and 18 deletions
|
@ -388,7 +388,6 @@ asan_sanitizer_task:
|
||||||
env:
|
env:
|
||||||
CXXFLAGS: -DZEEK_DICT_DEBUG
|
CXXFLAGS: -DZEEK_DICT_DEBUG
|
||||||
ZEEK_CI_CONFIGURE_FLAGS: *ASAN_SANITIZER_CONFIG
|
ZEEK_CI_CONFIGURE_FLAGS: *ASAN_SANITIZER_CONFIG
|
||||||
ZEEK_CI_DISABLE_SCRIPT_PROFILING: 1
|
|
||||||
ASAN_OPTIONS: detect_leaks=1
|
ASAN_OPTIONS: detect_leaks=1
|
||||||
|
|
||||||
ubsan_sanitizer_task:
|
ubsan_sanitizer_task:
|
||||||
|
@ -403,7 +402,6 @@ ubsan_sanitizer_task:
|
||||||
env:
|
env:
|
||||||
CXXFLAGS: -DZEEK_DICT_DEBUG
|
CXXFLAGS: -DZEEK_DICT_DEBUG
|
||||||
ZEEK_CI_CONFIGURE_FLAGS: *UBSAN_SANITIZER_CONFIG
|
ZEEK_CI_CONFIGURE_FLAGS: *UBSAN_SANITIZER_CONFIG
|
||||||
ZEEK_CI_DISABLE_SCRIPT_PROFILING: 1
|
|
||||||
ZEEK_TAILORED_UB_CHECKS: 1
|
ZEEK_TAILORED_UB_CHECKS: 1
|
||||||
UBSAN_OPTIONS: print_stacktrace=1
|
UBSAN_OPTIONS: print_stacktrace=1
|
||||||
|
|
||||||
|
|
16
ci/test.sh
16
ci/test.sh
|
@ -59,13 +59,6 @@ function run_btests {
|
||||||
|
|
||||||
pushd testing/btest
|
pushd testing/btest
|
||||||
|
|
||||||
# Commenting out this line in btest.cfg causes the script profiling/coverage
|
|
||||||
# to be disabled. We do this for the sanitizer build right now because of a
|
|
||||||
# fairly significant performance bug when running tests.
|
|
||||||
if [ "${ZEEK_CI_DISABLE_SCRIPT_PROFILING}" = "1" ]; then
|
|
||||||
sed -i 's/^ZEEK_PROFILER_FILE/#ZEEK_PROFILER_FILE/g' btest.cfg
|
|
||||||
fi
|
|
||||||
|
|
||||||
${BTEST} -z ${ZEEK_CI_BTEST_RETRIES} -d -A -x btest-results.xml -j ${ZEEK_CI_BTEST_JOBS} || result=1
|
${BTEST} -z ${ZEEK_CI_BTEST_RETRIES} -d -A -x btest-results.xml -j ${ZEEK_CI_BTEST_JOBS} || result=1
|
||||||
make coverage
|
make coverage
|
||||||
prep_artifacts
|
prep_artifacts
|
||||||
|
@ -74,15 +67,6 @@ function run_btests {
|
||||||
}
|
}
|
||||||
|
|
||||||
function run_external_btests {
|
function run_external_btests {
|
||||||
# Commenting out this line in btest.cfg causes the script profiling/coverage
|
|
||||||
# to be disabled. We do this for the sanitizer build right now because of a
|
|
||||||
# fairly significant performance bug when running tests.
|
|
||||||
if [ "${ZEEK_CI_DISABLE_SCRIPT_PROFILING}" = "1" ]; then
|
|
||||||
pushd testing/external
|
|
||||||
sed -i 's/^ZEEK_PROFILER_FILE/#ZEEK_PROFILER_FILE/g' subdir-btest.cfg
|
|
||||||
popd
|
|
||||||
fi
|
|
||||||
|
|
||||||
local zeek_testing_pid=""
|
local zeek_testing_pid=""
|
||||||
local zeek_testing_pid_private=""
|
local zeek_testing_pid_private=""
|
||||||
pushd testing/external/zeek-testing
|
pushd testing/external/zeek-testing
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue