This happens after bd597c33e3e58cd3c6b22ed42f8f1fd7ff886bb2 in many pull requests as a silent merge conflict. For example:
- #29720 (comment)
- #29521 (comment)
- (Probably many undetected, because the CI task was not yet re-run)
- ...
This happens after bd597c33e3e58cd3c6b22ed42f8f1fd7ff886bb2 in many pull requests as a silent merge conflict. For example:
<!--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.
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.
utACK fa73431dd4709754c34a4d5ad1c940ff9e628cf3
16 | @@ -17,4 +17,4 @@ export RUN_FUNCTIONAL_TESTS=false 17 | export GOAL="install" 18 | # -Wno-psabi is to disable ABI warnings: "note: parameter passing for argument of type ... changed in GCC 7.1" 19 | # This could be removed once the ABI change warning does not show up by default 20 | -export BITCOIN_CONFIG="--enable-reduce-exports CXXFLAGS=-Wno-psabi" 21 | +export BITCOIN_CONFIG="--enable-reduce-exports CXXFLAGS='-Wno-psabi -Wno-error=maybe-uninitialized'"
Good to see. Might be worth adding a comment about why the warning is disabled here and in ci/test/00_setup_env_win64.sh?
All -Wno-error= in ./ci/ are due to false positives. I may address this, if I have to re-push for other reasons.
lgtm
ACK fa73431dd4709754c34a4d5ad1c940ff9e628cf3 - many fixed with 13.x
Ported to the CMake-based build system in https://github.com/hebasto/bitcoin/pull/207.