Merged
Conversation
ansel1
force-pushed
the
artifactsdir
branch
9 times, most recently
from
0cf636d to
0cbfdb6
Compare
…ine them in the log output
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
1 participant
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.
Supports the new -artifacts flag in go1.26: if set, logs for each test will be saved to $artifactDir/flumetest/flumetest_.log
It also backfills
-artifactsflag for older versions of go, so you can start usinggo test -artifactsbefore upgrading to go1.26.The artifact dir defaults to $outputDir (another test flag), which defaults to cwd.
If
-artifactsis not set, logs are inlined in the test log as usual.