On 200831 1732, Thomas Huth wrote: > The fuzzer job finishes quite early, so we can run the unit tests and > qtests with -fsanitize=address here without extending the total test time. >
Sounds good to me, though its too bad that this is limited to i386 and we aren't using the --enable-sanitizers configure argument due to the strange oss-fuzz build script. Speaking of testing with sanitizers, does it make sense to have a job that does check-qtest with --enable-tsan, now that we have ThreadSanitizer support? Can --enable-sanitizers --enable-tsan be added to some existing job, without severely increasing the pipeline's exeuction time? Reviewed-by: Alexander Bulekov <alx...@bu.edu> > Signed-off-by: Thomas Huth <th...@redhat.com> > --- > .gitlab-ci.yml | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) > > diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml > index 17f1f8fad9..417fda6909 100644 > --- a/.gitlab-ci.yml > +++ b/.gitlab-ci.yml > @@ -256,13 +256,14 @@ build-oss-fuzz: > - mkdir build-oss-fuzz > - CC="clang" CXX="clang++" CFLAGS="-fsanitize=address" > ./scripts/oss-fuzz/build.sh > + - export ASAN_OPTIONS="fast_unwind_on_malloc=0" > - for fuzzer in $(find ./build-oss-fuzz/DEST_DIR/ -executable -type f > | grep -v slirp); do > grep "LLVMFuzzerTestOneInput" ${fuzzer} > /dev/null 2>&1 || continue > ; > echo Testing ${fuzzer} ... ; > - ASAN_OPTIONS="fast_unwind_on_malloc=0" > - "${fuzzer}" -runs=1000 -seed=1 || exit 1 ; > + "${fuzzer}" -runs=1000 -seed=1 || exit 1 ; > done > + - cd build-oss-fuzz && make check-qtest-i386 check-unit > > build-tci: > <<: *native_build_job_definition > -- > 2.18.2 >