[libFuzzer] Remove hardcoded number of new features in merge_two_step.test.
authorMax Moroz <mmoroz@chromium.org>
Wed, 11 Sep 2019 19:43:03 +0000 (19:43 +0000)
committerMax Moroz <mmoroz@chromium.org>
Wed, 11 Sep 2019 19:43:03 +0000 (19:43 +0000)
Summary:
The number of features can be different on different platforms.

This should fixed broken builders, e.g.
http://lab.llvm.org:8011/builders/clang-cmake-aarch64-full/builds/7946

Reviewers: Dor1s

Reviewed By: Dor1s

Subscribers: kristof.beyls, delcypher, #sanitizers, llvm-commits

Tags: #llvm, #sanitizers

Differential Revision: https://reviews.llvm.org/D67458

llvm-svn: 371647

compiler-rt/test/fuzzer/merge_two_step.test

index 42abe0b..fbbd2a5 100644 (file)
@@ -10,7 +10,7 @@ RUN: echo ..Z... > %t/T1/3
 RUN: rm -f %t/MCF
 RUN: %run %t-FullCoverageSetTest -merge=1 -merge_control_file=%t/MCF %t/T0 %t/T1 2>&1 | FileCheck %s --check-prefix=CHECK1
 CHECK1: MERGE-OUTER: 3 files, 0 in the initial corpus
-CHECK1: MERGE-OUTER: 3 new files with 11 new features added; 11 new coverage edges
+CHECK1: MERGE-OUTER: 3 new files with {{.*}} new features added; 11 new coverage edges
 
 RUN: echo ...Z.. > %t/T2/1
 RUN: echo ....E. > %t/T2/2
@@ -28,4 +28,4 @@ CHECK2: MERGE-OUTER: starting merge from scratch, but reusing coverage informati
 CHECK2: MERGE-OUTER: 7 files, 0 in the initial corpus, 3 processed earlier
 CHECK2: MERGE-INNER: using the control file 
 CHECK2: MERGE-INNER: 4 total files; 0 processed earlier; will process 4 files now
-CHECK2: MERGE-OUTER: 6 new files with 14 new features added; 14 new coverage edges
+CHECK2: MERGE-OUTER: 6 new files with {{.*}} new features added; 14 new coverage edges