diff options
| author | Jonathan Foote <jonathan@foote.pub> | 2020-06-16 12:18:02 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-06-16 09:18:02 -0700 |
| commit | bfa11be2f95d16c1c77e423589fdf8589865ec0d (patch) | |
| tree | f4d172dca6807f6a4a4987eccf61d364ccfe01f9 /docs/getting-started | |
| parent | d9c7f893f3e35757298e1cc9e5e8b7f7fb65fffb (diff) | |
| download | oss-fuzz-bfa11be2f95d16c1c77e423589fdf8589865ec0d.tar.gz | |
Explicitly define sanitizer support (#3995)
The oss-fuzz documentation states that listing supported sanitizers in a project's yaml [is optional](https://google.github.io/oss-fuzz/getting-started/new-project-guide/#sanitizers). It appears that CIFuzz requires supported sanitizers to be included in this file ([ref](https://github.com/google/oss-fuzz/blob/26e8d7c7728096edf55a1fb6d0ecbc4b2dae6afa/infra/cifuzz/cifuzz.py#L508-L529)). I believe this causes the CIFuzz Github Action to fail for projects that have not listed support for address sanitizer explicitly in their respective project YAML.
This PR explicitly defines support for asan and ubsan with a goal of fixing h2o's CIFuzz build
Diffstat (limited to 'docs/getting-started')
0 files changed, 0 insertions, 0 deletions