diff options
author | jonathanmetzman <31354670+jonathanmetzman@users.noreply.github.com> | 2020-05-13 12:44:11 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-05-13 12:44:11 -0700 |
commit | 1f533163ccb52fcbde052bfc0cffe75aadbce49b (patch) | |
tree | ce794986d206d0398c91b3d2baf4e714efafb0c3 /docs | |
parent | a019d8a7874f6f0fb845d25a95d6762980e5cf74 (diff) | |
download | oss-fuzz-1f533163ccb52fcbde052bfc0cffe75aadbce49b.tar.gz |
[CIFuzz] Support ALLOWED_BROKEN_TARGETS_PERCENTAGE (#3726)
Currently we use Github action's inputs as inputs to cifuzz.
This means we need to do an extra step to convert each input into
an env var so our scripts can actually use it.
This is pretty bug prone and unnecessary, we should probably
get rid of this abstraction and switch to encouraging devs to set
the env vars directly.
Diffstat (limited to 'docs')
-rw-r--r-- | docs/getting-started/continuous_integration.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/getting-started/continuous_integration.md b/docs/getting-started/continuous_integration.md index 2dbc2ad25..191eb47dc 100644 --- a/docs/getting-started/continuous_integration.md +++ b/docs/getting-started/continuous_integration.md @@ -90,6 +90,10 @@ CIFuzz will never report a failure even if it finds a crash in your project. This requires the user to manually check the logs for detected bugs. If dry run mode is desired, make sure to set the dry-run parameters in both the `Build Fuzzers` and `Run Fuzzers` action step. +`allowed_broken_targets_percentage`: Can be set if you want to set a stricter +limit for broken fuzz targets than OSS-Fuzz's check_build. Most users should +not set this. + ## Understanding results The results of CIFuzz can be found in two different places. |