mirror of https://github.com/google/oss-fuzz.git
[infra] Fix bad build check for UBSan since we compile engines without sanitizers now (fixes #1542).
This commit is contained in:
parent
7f26e2fd92
commit
52fe2acc1a
|
@ -30,8 +30,12 @@ ASAN_CALLS_THRESHOLD_FOR_NON_ASAN_BUILD=0
|
|||
MSAN_CALLS_THRESHOLD_FOR_MSAN_BUILD=1000
|
||||
MSAN_CALLS_THRESHOLD_FOR_NON_MSAN_BUILD=0
|
||||
|
||||
UBSAN_CALLS_THRESHOLD_FOR_UBSAN_BUILD=350
|
||||
UBSAN_CALLS_THRESHOLD_FOR_NON_UBSAN_BUILD=200
|
||||
# Usually, a non UBSan build (e.g. ASan) has 165 calls to UBSan runtime. The
|
||||
# majority of targets built with UBSan have 200+ UBSan calls, but there are
|
||||
# some very small targets that may have < 200 UBSan calls even in a UBSan build.
|
||||
# Use threshold value of 170 which should satisfy both cases with a little gap.
|
||||
UBSAN_CALLS_THRESHOLD_FOR_UBSAN_BUILD=170
|
||||
UBSAN_CALLS_THRESHOLD_FOR_NON_UBSAN_BUILD=170
|
||||
|
||||
|
||||
# Verify that the given fuzz target has proper coverage instrumentation.
|
||||
|
@ -65,7 +69,7 @@ function check_instrumentation {
|
|||
fi
|
||||
return
|
||||
else
|
||||
# TODO: add checks for another fuzzing engines if possible.
|
||||
# TODO: add checks for other fuzzing engines if possible.
|
||||
return
|
||||
fi
|
||||
|
||||
|
|
Loading…
Reference in New Issue