test/unpack_strategy: run extract with verbose#23070
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adjusts the UnpackStrategy extraction shared spec to run extracts in verbose mode to help diagnose an intermittent gunzip failure seen in portable CI runs.
Changes:
- Pass
verbose: truetoUnpackStrategy#extractin the shared#extractRSpec example to increase command output during test extraction.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
41d6ae9 to
58ce87e
Compare
carlocab
approved these changes
Jul 12, 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.
Currently Gzip is failing in portable PRs but I can't reproduce it. Adding verbose to see if it gives more useful information
https://github.com/Homebrew/homebrew-core/actions/runs/29179553748/job/86656464924#step:4:322
brewcommands to reproduce the bug?brew lgtm(style, typechecking and tests) locally?