[fuzz] add fuzz coverage CI check#11045
Conversation
Signed-off-by: Asra Ali <asraa@google.com>
Signed-off-by: Asra Ali <asraa@google.com>
|
@asraa Very cool. LMK when this passes; I'd like to take a look at the artifacts in CI. Are you planning on adding a gating check on overall fuzz coverage to encourage folks to write more fuzzers in this PR? |
|
/wait |
Signed-off-by: Asra Ali <asraa@google.com>
Signed-off-by: Asra Ali <asraa@google.com>
|
CI failure is interesting. An easy solution is to run the gtest mode of the fuzz target when running I pushed the server corpus entry that triggers the
@yanavlasov Does this indicate that this might be a compiler bug? Note: There are a lot of lambas in this stack... |
Signed-off-by: Asra Ali <asraa@google.com>
|
yeah I think we might want to hold this until we sort out multi-binary coverage #10909, I think that will get rid of most issues we hit with coverage. |
|
marking as draft, for both the clang issue and multibinary coverage |
|
This pull request has been automatically marked as stale because it has not had activity in the last 7 days. It will be closed in 7 days if no further activity occurs. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions! |
Signed-off-by: Asra Ali <asraa@google.com>
Signed-off-by: Asra Ali <asraa@google.com>
|
This is ready for review! Edit: Coverage report produced https://347756-65214191-gh.circle-artifacts.com/0/fuzz_coverage/index.html |
Signed-off-by: Asra Ali <asraa@google.com>
Signed-off-by: Asra Ali <asraa@google.com>
|
:/ There's a regression from a recent PR submitted. Will ping when it's resolved. |
|
H/2 test timeout is blocking CI: #11290. Will merge master when fix is merged |
Signed-off-by: Asra Ali <asraa@google.com>
|
Fuzz CI passes when I build with size optimization (ASSERTs are still caught) |
Signed-off-by: Asra Ali <asraa@google.com>
Signed-off-by: Asra Ali <asraa@google.com>
Signed-off-by: Asra Ali <asraa@google.com>
Signed-off-by: Asra Ali <asraa@google.com>
|
|
The close was by accident. It turns out interns are also running into this issue locally #11802 I got coverage without asan working, so i'll make that fix a separate PR and reopen this when when it's ready. |
Signed-off-by: Asra Ali <asraa@google.com>
Signed-off-by: Asra Ali <asraa@google.com>
Signed-off-by: Asra Ali <asraa@google.com>
Signed-off-by: Asra Ali <asraa@google.com>
Signed-off-by: Asra Ali <asraa@google.com>
Signed-off-by: Asra Ali <asraa@google.com>
Signed-off-by: Asra Ali <asraa@google.com>
Signed-off-by: Asra Ali <asraa@google.com>
|
Finally, success. using fuzzer-no-link in bazelrc cli breaks the gtest that's used to build the corpus, hence why it's removed. |
| COVERAGE_TARGETS=//test/... | ||
| fi | ||
|
|
||
| if [[ "${FUZZ_COVERAGE}" == "true" ]]; then |
There was a problem hiding this comment.
This if has the same condition as the next if block. Can they be merged?
ci/do_ci.sh
Outdated
|
|
||
| # Reduce the amount of memory Bazel tries to use to prevent it from launching too many subprocesses. | ||
| # This should prevent the system from running out of memory and killing tasks. See discussion on | ||
| # https://github.com/envoyproxy/envoy/pull/5611. | ||
| [ -z "$CIRCLECI" ] || export BAZEL_BUILD_OPTIONS="${BAZEL_BUILD_OPTIONS} --local_ram_resources=12288" | ||
|
|
Signed-off-by: Asra Ali <asraa@google.com>
Commit Message: Add `bazel.fuzz_coverage` to CI. Publishes fuzz coverage report in `coverage_publish` Risk Level: Medium Testing: Local testing of `./ci/run_envoy_docker.sh './ci/do_ci.sh bazel.fuzz_coverage'`, as well as `FUZZ_COVERAGE=true test/run_envoy_bazel_coverage.sh` with single test args/directory, VALIDATE on/off. Fixes: envoyproxy#9573 Docs: Updated bazel/README.md and fuzz/README.md for docs about running local coverage. Signed-off-by: Asra Ali <asraa@google.com> Signed-off-by: Kevin Baichoo <kbaichoo@google.com>
Commit Message: Add `bazel.fuzz_coverage` to CI. Publishes fuzz coverage report in `coverage_publish` Risk Level: Medium Testing: Local testing of `./ci/run_envoy_docker.sh './ci/do_ci.sh bazel.fuzz_coverage'`, as well as `FUZZ_COVERAGE=true test/run_envoy_bazel_coverage.sh` with single test args/directory, VALIDATE on/off. Fixes: envoyproxy#9573 Docs: Updated bazel/README.md and fuzz/README.md for docs about running local coverage. Signed-off-by: Asra Ali <asraa@google.com> Signed-off-by: scheler <santosh.cheler@appdynamics.com>
Commit Message: Add
bazel.fuzz_coverageto CI. Publishes fuzz coverage report incoverage_publishRisk Level: Medium
Testing: Local testing of
./ci/run_envoy_docker.sh './ci/do_ci.sh bazel.fuzz_coverage', as well asFUZZ_COVERAGE=true test/run_envoy_bazel_coverage.shwith single test args/directory, VALIDATE on/off.Fixes: #9573
Docs: Updated bazel/README.md and fuzz/README.md for docs about running local coverage.
Signed-off-by: Asra Ali asraa@google.com