-
Notifications
You must be signed in to change notification settings - Fork 5
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
Reuse external workflows in Fuzzer CI #29
Reuse external workflows in Fuzzer CI #29
Conversation
e11ec51
to
83c353d
Compare
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.
Just one comment, otherwise it looks good
data: ${{ matrix.data }} | ||
timeout-minutes: 20 | ||
max_queries: 10 | ||
dry: false |
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.
dry should be true I think
dry
is basically meant to mean that the program should be run without attempting to alter any github issues.
If we want to test that the fuzzer CI still works, we want to test that the fuzzer CI debug build can be built, but we don't need to file any github issues or check other issues
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.
Done
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.
thanks!
This PR makes
test-fuzzer
reuseBuild DuckDB
andFuzzer
workflows and connected to the #22