fix(base-tar): skip GNU-sparse tar test when only bsdtar is available - #101
Merged
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
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.
TarInputStreamTests#shouldReadGnuSparseFileshelled out totar --sparse, which fails on macOS because the systemtarthere isbsdtarand doesn't understand the GNU--sparseflag.The test now calls a new
findGnuTarBinary()helper that probestarand thengtar(the name Homebrew'sgnu-tarinstalls under) by running--versionand checking the output forGNU tar. If neither resolves to a real GNU tar, the test skips itself viaAssumptions.assumeTruewith a message explaining why, instead of failing outright.