Repository navigation
sqlsmith: Ignore jq program errors - #39895
Merged
frankmcsherry merged 1 commit intoOct 16, 2026
Merged
Conversation
SQLsmith passes arbitrary strings as jq programs, which fail to parse or evaluate, and non-literal programs, which the planner rejects. Both are expected and not product bugs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
2 participants
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.
The
jqfunction (#39838) is now enabled in CI, and SQLsmith fails both nightly SQLsmith jobs on errors it creates itself. It passes arbitrary strings as jq programs, which fail to parse or evaluate (jq: ...). It also passes non-literal programs, which the planner rejects. This adds both messages toknown_errors, which parallel workload also uses.Seen in nightly 18509 and 18510, and in release qualification 1400.
🤖 Generated with Claude Code