GitHub user roseduan added a comment to the discussion: [Proposal] Continuous
SQLancer fuzzing for Cloudberry (5 bugs from a first run, looking for
volunteers)
Proposal: add a GitHub Actions workflow that runs SQLancer against main,
separate
from the PR CI:
- Triggers: a weekly schedule and manual workflow_dispatch only. It does not
run
on PRs or pushes and is not a required check, like coverity.yml.
- Runs only in apache/cloudberry (repository_owner check), not in forks.
- Builds main in the existing build container, creates the demo cluster and
runs
the NoREC, TLP, PQS and DQP oracles with a fixed SQLancer commit.
- Cost: one runner, about N hours per week, with a hard timeout.
- On failure: upload SQLancer and server logs as artifacts.
How do you think?
@my-ship-it @tuhaihe
GitHub link:
https://github.com/apache/cloudberry/discussions/1952#discussioncomment-19057879
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
