GH-48275: [C++][Dev] Allow choosing verbosity when fuzzing #48276
+44
−42
Conversation
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
Member
Author
|
@github-actions crossbow submit fuzz |
|
Revision: ced1065 Submitted crossbow builds: ursacomputing/crossbow @ actions-26001fe640
|
Introduce an environment variable `ARROW_FUZZING_VERBOSITY` that allows choosing whether fuzzing errors are logged or silenced.
pitrou
force-pushed
the
gh48275-fuzz-verbosity
branch
from
ced1065 to
30989c1
Compare
adamreeve
approved these changes
Dec 2, 2025
github-actions
bot
added
awaiting committer review
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
What changes are included in this PR?
Introduce an environment variable
ARROW_FUZZING_VERBOSITYthat allows choosing whether fuzzing errors are logged or silenced.Also slight internal API simplification using
std::string_view.Are these changes tested?
Manually.
Are there any user-facing changes?
No.