From 415ae4df51b1b92d36d8a06192a4816ba936fea5 Mon Sep 17 00:00:00 2001 From: Ruud van Asseldonk Date: Sun, 28 May 2017 13:31:06 +0200 Subject: [PATCH] Disable fuzzing on CI for now, it is broken Libfuzzer does not load the corpus, even when it has been populated. And starting from scratch every time is not very useful; a decent corpus is required to find the interesting paths. Fuzzing from an empty corpus every time is not going to uncover newly introduced bugs. --- .travis.yml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/.travis.yml b/.travis.yml index 187da30..ee441ca 100644 --- a/.travis.yml +++ b/.travis.yml @@ -23,7 +23,8 @@ cache: directories: # Cache the fuzzing corpus, so it does not have to discover the entire corpus # again every time, and it can focus on finding bugs instead. - - fuzz_corpus + # TODO: This is broken, libfuzzer seems to not recognize the corpus somehow. + # - fuzz_corpus # Cache the test samples to not put so much load on archive.org, but on # Travis' S3 buckets instead. @@ -38,4 +39,5 @@ script: - cargo test # On the nightly configuration, fuzz for 15 minutes. - - FUZZ_SECONDS=900 tools/fuzz_on_ci.sh + # TODO: This is broken, libfuzzer does not recognize the cached corpus. + # - FUZZ_SECONDS=900 tools/fuzz_on_ci.sh