diff options
| author | Brent Cook <busterb@gmail.com> | 2023-07-07 08:34:16 +0300 |
|---|---|---|
| committer | Brent Cook <busterb@gmail.com> | 2023-07-07 08:34:16 +0300 |
| commit | e1d6f782966399be59a0c15deb051f8f11fa6ebd (patch) | |
| tree | aca9a9026eff419619bbf3b3490989140c68db5d | |
| parent | 4aa76421303aaddbae7da8cf76549d5c0f1419be (diff) | |
| download | portable-e1d6f782966399be59a0c15deb051f8f11fa6ebd.tar.gz portable-e1d6f782966399be59a0c15deb051f8f11fa6ebd.tar.bz2 portable-e1d6f782966399be59a0c15deb051f8f11fa6ebd.zip | |
change the trigger for running fuzzer tests
Since fuzzers benefit more from being run regularly on the openbsd tree,
and they take a long time, does it make more sense that the trigger is a
cron like the Coverity job? They sometimes don't work in branches anyway,
since the fuzz builds rely on external code being updated to match
the master branch.
| -rw-r--r-- | .github/workflows/cifuzz.yml | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/.github/workflows/cifuzz.yml b/.github/workflows/cifuzz.yml index 8c25624..bdb3b2c 100644 --- a/.github/workflows/cifuzz.yml +++ b/.github/workflows/cifuzz.yml | |||
| @@ -1,5 +1,10 @@ | |||
| 1 | name: CIFuzz | 1 | name: CIFuzz |
| 2 | on: [pull_request] | 2 | |
| 3 | on: | ||
| 4 | workflow_dispatch: | ||
| 5 | schedule: | ||
| 6 | - cron: "0 0 * * *" | ||
| 7 | |||
| 3 | jobs: | 8 | jobs: |
| 4 | Fuzzing: | 9 | Fuzzing: |
| 5 | runs-on: ubuntu-latest | 10 | runs-on: ubuntu-latest |