Skip to content

ci: make Deep Fuzzing actually run 8 hours per target #33

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
27Bslash6 merged 1 commit into from
May 23, 2026
Merged

ci: make Deep Fuzzing actually run 8 hours per target #33

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions .github/workflows/security.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -126,6 +126,7 @@ jobs:
name: Deep Fuzzing (8 hours)
runs-on: cachekit
if: github.event_name == 'schedule'
timeout-minutes: 540
strategy:
fail-fast: false
matrix:
Expand Down Expand Up @@ -172,13 +173,13 @@ jobs:
# nightly rustc rejects. Let cargo resolve fresh deps.
run: cargo install cargo-fuzz

- name: Run deep fuzz (30 minutes per target)
- name: Run deep fuzz (8 hours per target)
run: |
cd fuzz
# Build first - fail fast on compile errors
cargo fuzz build ${{ matrix.target }}
# Run fuzz - timeout exit code 124 is acceptable (means it ran the full duration)
timeout 1800 cargo fuzz run ${{ matrix.target }} -- -max_total_time=1800 || [ $? -eq 124 ]
timeout 28800 cargo fuzz run ${{ matrix.target }} -- -max_total_time=28800 || [ $? -eq 124 ]

- name: Upload crash artifacts
if: always()
Expand Down
Loading