ci: add scheduled fuzz testing workflow - #744
Open
mliem2k wants to merge 1 commit into
Open
Conversation
Add a nightly scheduled GitHub Actions job that builds Bolt with test utilities enabled and runs the existing expression, aggregation, window, and join fuzzer binaries for a bounded duration each. This complements per-PR CI, which does not exercise these fuzzers, and follows the same self-hosted runner and container conventions used by the existing build-main and build-test workflows.
|
|
This file contains hidden or 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
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.
What problem does this PR solve?
Issue Number: close #115
Type of Change
Description
Bolt already ships several Velox derived fuzzers (expression, aggregation, window, join, parquet, connector, vector), but none of them are wired into CI today, so they only catch bugs when someone remembers to run them manually. This adds a nightly scheduled workflow,
.github/workflows/scheduled-fuzz-tests.yml, that builds Bolt once with test utilities enabled and then runs seven of the existing fuzzer binaries for a bounded duration each, in parallel, via a matrix job:Each binary is located dynamically under
_build/Releasewithfindrather than a hardcoded path, so the workflow does not break if the CMake output layout changes. Duration is controlled by aFUZZ_DURATION_SECenv var, defaulting to 1800 seconds and overridable viaworkflow_dispatchfor manual runs. On failure, any reproducer output under/tmp/velox_*or/tmp/bolt_*is uploaded as a build artifact to aid triage.The job reuses the exact runner, container image, and conan service conventions already used in
build-main.ymlandbuild-test.yml(self-hosted, mediumrunner,bolt-registry:5000/bolt-ciimage,bolt-build-basecomposite action,make release_spark_with_test), so it fits the existing CI setup rather than introducing a new pattern.Scope was kept intentionally narrow to what issue #115 asks for. Additional fuzz targets that already exist in the tree (parquet, exchange, connector, vector) were left out of this first pass and can be added later if useful.
Note: issue #114 (scheduled ASAN builds) was not addressed in this PR. It already has an open PR (#656) covering the same scope, so I did not duplicate that effort.
Performance Impact
Release Note
Release Note:
Checklist (For Author)
Breaking Changes