gh: Allow manual running of the full test suite and erlfuzz #7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This change introduces two new features:
- Comment "/run-fuzzer" on a pull request to trigger a bot which will
run erlfuzz and report the results by replying on the comment
thread
- Add the "full-build-and-check" tag to a pull request to
force-override CI to always run tests for all applications
The two differ in how they are expressed because I have worked on the
basis that:
- Running the fuzzer is expensive, so we probably want to try to limit
that to when we know we really need it and explicitly invoke it.
- Running tests for all apps is sometimes needed because the existing
mechanism for selecting apps to test is unsound: If you modify
stdlib, apps that depend on it won't be analysed, but stdlib itself
will. As such, using a tag means that all subsequent test runs for
that pull request will return the full signal.
This change also factors out the initial build of OTP in CI into
`base-build.yaml` so that it can be reused elsewhere, for example,
when running erlfuzz.
The mechanism of using comments to execute manual CI jobs could
later be extended to add other optional or expensive jobs (e.g.
eqWAlizer) so that there is an official means of running them, without
requiring that they be part of the usual, automatic CI suite.
TD5
force-pushed
the
manual-fuzzing-and-full-testing
branch
from
ad87d5b to
602d9f8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change introduces two new features:
The two differ in how they are expressed because I have worked on the basis that:
This change also factors out the initial build of OTP in CI into
base-build.yamlso that it can be reused elsewhere, for example, when running erlfuzz.The mechanism of using comments to execute manual CI jobs could later be extended to add other optional or expensive jobs (e.g. eqWAlizer) so that there is an official means of running them, without requiring that they be part of the usual, automatic CI suite.