Fabian Meumertzheim

The engine-agnostic launcher doesn't support passing through fuzzer-specific flags atm, but in order to run e.g. the target `//examples/java:FuzzTest`, you could try: ``` bazel run //examples/java:FuzzTest_bin -- -use_value_profile=1 ``` Note...

Caused by https://github.com/bazelbuild/bazel/issues/15667, will need to wait for that to be resolved in a rules_kotlin release.

Looks like the change has been rolled back (see also https://bazelbuild.slack.com/archives/CA31HN1T3/p1643719616408949), so we there is no need for immediate action.

@stefanbucur It's still relevant, but not urgent: https://github.com/bazel-contrib/SIG-rules-authors/issues/11#issuecomment-1029861300 I don't seem to have rights to reopen.

The Jazzer bug caused a crash if the fuzz target wasn't executed with a `-seed` argument. Both the bad build check and all our internal tests did that for the...

@oliverchang With empty input, do you mean an invocation of the form `fuzz_target empty_file`? If so, that would have caught the issue and I can add it in a PR.

@oliverchang I don't see how the test failure is related to my change as it diffs cloud build steps. Do you know what could cause it?

Will do. @oliverchang If this check is mostly meant to apply to Jazzer, Atheris and potential future wrappers, maybe limiting the check to fuzzing languages other than C/C++ could help...

@oliverchang Some of the checks fail with: ``` 2022-09-09T14:50:01.9843353Z ERROR: /src/centipede/BUILD:502:8: Compiling blob_file_test.cc failed: (Exit 1): clang-15 failed: error executing command /usr/local/bin/clang-15 -U_FORTIFY_SOURCE -fstack-protector -Wall -Wthread-safety -Wself-assign -Wunused-but-set-parameter -Wno-free-nonheap-object -fcolor-diagnostics...

@oliverchang Looks good now.