message: Fuzz tests: only worry about crashes.
  It is ok if our formatter fails for other reasons (that should be
  addressed in different tests and functional implementations). Our
  main criteria for the fuzzer passing is that we do not crash.
diff: @@ -18362,14 +18362,22 @@ constexpr absl::string_view string_view_from_literal(const char (&s)[N]) {
  FormatStyle style;
  std::ostringstream stream;
  const auto status = FormatVerilog(input, "<filename>", style, stream);
  - EXPECT_OK(status) << "Reason: " << status.message() << "\nEscaped input: \""
  + // If we are here, we did at least not crash, which is all we desire for
  + // the fuzzer tests.
  + // Other issues that are reported correctly (probably due to strange inputs
  + // generated by the fuzzer) are ok, so we just log them here FYI.
  + if (!status.ok()) {
  + LOG(INFO) << "No crash, but format failed for other reason: "
  + << status.message() << "\nEscaped input: \""
  << EscapeString(input) << "\"";
  }
  +}
  #if 0
  // https://github.com/chipsalliance/verible/issues/1381
  TEST(FormatterEndToEndTest, FuzzingRegression_1381) {
  - TestForNonCrash({"P#(\0\0//\0//\0,);", 14});
  + TestForNonCrash(string_view_from_literal("P#(\0\0//\0//\0,);"));
  + TestForNonCrash(string_view_from_literal("P#(\0\0//\0,,//\0,"));
  }
  #endif
  @@ -18380,14 +18388,10 @@ TEST(FormatterEndToEndTest, FuzzingRegression_UseAfterFree_1384) {
  // https://github.com/chipsalliance/verible/issues/1386
  TEST(FormatterEndToEndTest, FuzzingRegressionHierachyInvariant) {
  -#if 0
  // Original sample input from fuzzer
  TestForNonCrash(string_view_from_literal("`c(`c()\0;);"));
  -#endif
  -#if 0
  // Lexically correct variant (`\0` -> `\n`)
  TestForNonCrash(string_view_from_literal("`c(`c()\n;);"));
  -#endif
  // Lexically correct variant (`\0` removed)
  TestForNonCrash(string_view_from_literal("`c(`c(););"));
  }
  