From c43d00fa345b1af88f44af89152b58ef90075eda Mon Sep 17 00:00:00 2001 From: Andrew Brown Date: Fri, 26 Mar 2021 11:01:13 -0700 Subject: [PATCH] doc: link to where oss-fuzz issues are recorded (#2780) --- docs/contributing-ci.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/contributing-ci.md b/docs/contributing-ci.md index c7b422ca0e..5b7306f661 100644 --- a/docs/contributing-ci.md +++ b/docs/contributing-ci.md @@ -46,7 +46,8 @@ run on CI looks like this: corpus](https://github.com/bytecodealliance/wasmtime-libfuzzer-corpus) and run it through the fuzzers. This is mostly intended to be a pretty quick regression test and testing the fuzzers still build, most of our fuzzing - happens on [oss-fuzz](https://oss-fuzz.com). + happens on [oss-fuzz](https://oss-fuzz.com). Found issues are recorded in + the [oss-fuzz bug tracker](https://bugs.chromium.org/p/oss-fuzz/issues/list?q=-status%3AWontFix%2CDuplicate%20-component%3AInfra%20proj%3Awasmtime&can=1) While we do run more tests here and there, this is the general shape of what you can be expected to get tested on CI for all commits and all PRs. You can of