Truncate discovery command log#84
Merged
Merged
Conversation
gnufede
approved these changes
Jun 15, 2026
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
Truncate the test discovery command log value to 300 characters and log it as a single
commandfield.Why
When test discovery receives many explicit files, the logged argument list can become very long and noisy. Capping the logged command keeps the discovery log readable without changing the command that is actually executed.
E2E testing
Run
ddtest planin a project where the test discovery exclude pattern leaves many explicit test files, then verify theDiscovering tests with commandlog line is capped at 300 characters and discovery still completes.Validation run:
go test ./internal/discoverymake testmake lint