Remove cifuzz references

README.md

@@ -88,14 +88,6 @@ class ParserTests {
 
 A complete Maven example project can be found in [`examples/junit`](examples/junit).
 
-### CI Fuzz
-
-The open-source CLI tool [cifuzz](https://github.com/CodeIntelligenceTesting/cifuzz) makes
-it easy to set up Maven and Gradle projects for fuzzing with Jazzer.
-It provides a command-line UI for fuzzing runs, deduplicates and manages findings, and
-provides coverage reports for fuzz tests. Moreover, you can use CI Fuzz to run your fuzz
-tests at scale in the [CI App](https://app.code-intelligence.com).
-
 ### GitHub releases
 
 You can also use GitHub release archives to run a standalone Jazzer binary that starts its own JVM configured for fuzzing:

docs/common.md

@@ -12,7 +12,7 @@
 ### Recommended JVM options
 
 The following JVM settings are recommended for running Jazzer within JUnit.
-Both `cifuzz` and the `jazzer` launcher binary set them automatically.
+The `jazzer` launcher binary sets them automatically.
 
 * `-XX:-OmitStackTraceInFastThrow` ensures that stack traces are emitted even on hot code paths.
   This may hurt performance if your fuzz test frequently throws and catches exceptions, but also helps find flaky bugs.

docs/junit-integration.md

@@ -78,7 +78,7 @@ The tests from the resources directory are gathered by `walkInputs`. This will l
 JUnit will use the file's name as the name of the test case for its reporting. It also accepts .jar files where it will
 search with the given directory in the jar.
 
-### CIFuzz Corpus
+### Corpus
 
 The corpus kept in `.cifuzz-corpus/<test class name>/<test method name>` holds any inputs that libfuzzer found worth
 saving and not necessarily just inputs that caused a crash. Jazzer is able to set the directory but the contents of

src/main/java/com/code_intelligence/jazzer/junit/FuzzTestExecutor.java

@@ -190,8 +190,7 @@ private static Path addInputAndSeedDirs(
             .toAbsolutePath();
 
     // Use the specified corpus dir, if given, otherwise store the generated corpus in a per-class
-    // directory under the project root, just like cifuzz:
-    // https://github.com/CodeIntelligenceTesting/cifuzz/blob/bf410dcfbafbae2a73cf6c5fbed031cdfe234f2f/internal/cmd/run/run.go#L381
+    // directory under the project root.
     // The path is specified relative to the current working directory, which with JUnit is the
     // project directory.
     Path generatedCorpusDir = baseDir.resolve(generatedCorpusPath(fuzzTestClass, fuzzTestMethod));