-
Notifications
You must be signed in to change notification settings - Fork 446
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.
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
Fix fuzzer.bash script and entrypoint in docker file #2102
Conversation
Create Release CI workflow, implement timeout in fuzzing script and add it to release ci workflow
.github/workflows/release-ci.yml
Outdated
workflow_dispatch: | ||
merge_group: | ||
pull_request: | ||
push: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it make since to use
on:
release:
types: [created, published]
instead? That way you don't need to check for release label either.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed to that.
My reasoning behind having label that triggers it was for the case where one makes big changes and wants to run more exhaustive testing without creating a release.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What you said actually makes more sense rather than triggering on actual release. What do you think about just having it trigger on workflow_dispatch
for now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SG, changed to that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Currently running the nitro-fuzzer docker doesn't do anything, it silently fails without error code or a log.