Minor: Add note about SQLLancer fuzz testing to docs #11430
Merged
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.
Which issue does this PR close?
Part of #7013
Rationale for this change
@2010YOUY01 had done some great work for SQLLancer -- see #11030. It has found all sorts of corner case bugs (also kudos to @jonahgao for fixing many of them). This is a big step forward for a maturing engine.
(also it is getting added to sqlancer/sqlancer#954)
What changes are included in this PR?
Document the use of sql lancer based fuzzing to help make it more discoverable
Are these changes tested?
Doc CI
Are there any user-facing changes?