Skip to content

[SKIP SOF-TEST] Remove old fuzzer #7675

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
cujomalainey merged 1 commit into from
May 25, 2023
Merged

[SKIP SOF-TEST] Remove old fuzzer #7675

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
33 changes: 0 additions & 33 deletions .github/workflows/ipc_fuzzer.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,39 +10,6 @@ on: [pull_request, workflow_dispatch]

jobs:


# For the actual fuzzer see tools/oss-fuzz/README.
# also see
# https://google.github.io/oss-fuzz/getting-started/continuous-integration/
#
# Build and run fuzzer for 5s just to check that it runs properly. If it
Copy link
Contributor

@cujomalainey cujomalainey May 23, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this line still not true?

Copy link
Contributor Author

@andyross andyross May 23, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is, but it's "3m" now and done with the newer rig

Copy link
Contributor

@cujomalainey cujomalainey May 24, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why 3m? We just want to smoke test in this CI and let OSS-fuzz handle the longer runs

# consistently fails in under 5s you probably did something wrong

# If you came here to quickly copy/paste the invocation of some build
# script in order to reproduce a failure reported by github then you
# will be disappointed by the Github Action below: it's magical. For a
# thorough reproduction you must follow the links above. For a quick,
# dirty and incomplete reproduction hack you can try the following two
# lines. Don't do this at home.
#
# OUT=unused_dir cmake -B oss-fuzz-build/ -S tools/oss-fuzz/
# make -j -C oss-fuzz-build sof_ep fuzz_ipc.o
ipc-fuzzer-build:
runs-on: ubuntu-latest
steps:
- name: Build Fuzzers
uses: google/oss-fuzz/infra/cifuzz/actions/build_fuzzers@master
with:
oss-fuzz-project-name: 'sound-open-firmware'

- name: Run Fuzzers
uses: google/oss-fuzz/infra/cifuzz/actions/run_fuzzers@master
with:
oss-fuzz-project-name: 'sound-open-firmware'
language: c
fuzz-seconds: 5

# Newer fuzzer
simple-IPC-fuzz_sh:
runs-on: ubuntu-22.04
strategy:
Expand Down