Homebrew's warnings are quite noisy on the master branch:
This PR silents them to allow us to focus on other CI infra warnings once they happen.
Similar to https://github.com/bitcoin-core/secp256k1/pull/1578.
Homebrew's warnings are quite noisy on the master branch:
This PR silents them to allow us to focus on other CI infra warnings once they happen.
Similar to https://github.com/bitcoin-core/secp256k1/pull/1578.
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--006a51241073e994b41acfe9ec718e94-->
For detailed information about the code coverage, see the test coverage report.
<!--021abf342d371248e50ceaed478a90ca-->
See the guideline for information on the review process.
| Type | Reviewers |
|---|---|
| ACK | willcl-ark, tdb3 |
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.
utACK 032ebe5be4dfc3eb3d3693f1284fac6458bacbf3
lgtm
cr ut ACK 032ebe5be4dfc3eb3d3693f1284fac6458bacbf3
103 | @@ -104,8 +104,8 @@ jobs: 104 | HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK: 1 105 | run: | 106 | # A workaround for "The `brew link` step did not complete successfully" error. 107 | - brew install python@3 || brew link --overwrite python@3 108 | - brew install automake libtool pkg-config gnu-getopt ccache boost libevent miniupnpc libnatpmp zeromq qt@5 qrencode 109 | + brew install --quiet python@3 || brew link --overwrite python@3
Are these Qt workarounds still needed? Would be good if we could drop them, rather than adding more code to suppress warnings coming from workarounds that may no-longer be needed.