e1d6f78296
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.
32 lines
743 B
YAML
32 lines
743 B
YAML
name: CIFuzz
|
|
|
|
on:
|
|
workflow_dispatch:
|
|
schedule:
|
|
- cron: "0 0 * * *"
|
|
|
|
jobs:
|
|
Fuzzing:
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- name: Build Fuzzers
|
|
id: build
|
|
uses: google/oss-fuzz/infra/cifuzz/actions/build_fuzzers@master
|
|
with:
|
|
oss-fuzz-project-name: 'libressl'
|
|
dry-run: false
|
|
language: c++
|
|
- name: Run Fuzzers
|
|
uses: google/oss-fuzz/infra/cifuzz/actions/run_fuzzers@master
|
|
with:
|
|
oss-fuzz-project-name: 'libressl'
|
|
fuzz-seconds: 300
|
|
dry-run: false
|
|
language: c++
|
|
- name: Upload Crash
|
|
uses: actions/upload-artifact@v3
|
|
if: failure() && steps.build.outcome == 'success'
|
|
with:
|
|
name: artifacts
|
|
path: ./out/artifacts
|