-
Notifications
You must be signed in to change notification settings - Fork 38.7k
ci: Update "Win64 native" task #26891
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Dependency changes (2022.09.27 - 2023.01.09): - boost 1.80.0#0 -> 1.81.0#0 - libevent 2.1.12#6 -> libevent 2.1.12#7 - sqlite3 3.39.2#0 -> 3.40.0#1
|
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. ReviewsSee the guideline for information on the review process. |
| install_tools_script: | ||
| - choco install --yes --no-progress ccache --version=4.6.1 | ||
| - choco install --yes --no-progress ccache --version=4.7.4 | ||
| - choco install --yes --no-progress python3 --version=3.9.6 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit, realized after merge: I guess it should be fine to bump this as well, so that everything is still pinned but bumped to the latest version. (And add a comment that bumping to the latest in this file is fine?)
Finally, a two line patch could be squashed into one commit, but no big deal.
|
FWIW, the recent ccache 4.8.1 seems broken. Note the cacheable calls ratio: |
I found the reason that ccache >= 4.8 is not working as expected. We need to have However, in the light of upcoming CMake-based build system, I see no reasons to change our current |
6d05c4f msvc: Specify `boost-date-time` package explicitly (Hennadii Stepanov) 1f97e51 msvc: Update vcpkg manifest baseline up to "2023.08.09 Release" (Hennadii Stepanov) 2d2ef2f msvc: No need to specify the default feature for `libevent` package (Hennadii Stepanov) Pull request description: Last time we updated dependency packages used when compiling with MSVC in bitcoin/bitcoin#26891. Then we [switched](bitcoin/bitcoin#27335) to specifying the `builtin-baseline` in the `vcpkg.json` manifest file, which made checking out the entire vcpkg repository to a specific commit or tag unneeded. This PR updates the manifest baseline from [2023.01.09](https://github.com/microsoft/vcpkg/releases/tag/2023.01.09) to [2023.08.09](https://github.com/microsoft/vcpkg/releases/tag/2023.08.09): - berkeleydb: 4.8.30#8 --> 4.8.30#9 - boost: 1.81.0 --> 1.82.0#2 - sqlite3: 3.40.0#1 --> 3.42.0#1 - zeromq: 4.3.4#6 --> 2023-06-20#1 The most recent https://github.com/microsoft/vcpkg/releases/tag/2023.11.20 tag is still unavailable in the vcpkg installation in the current GHA Windows image (the head commit is microsoft/vcpkg@2b14b60 only). The other https://github.com/microsoft/vcpkg/releases/tag/2023.10.19 tag [introduces](boostorg/process@0c42a58) a warning C4297 in the Boost.Process 1.83 that is [fixed](boostorg/process#340) in the upcoming version 1.84. ACKs for top commit: fanquake: ACK 6d05c4f Tree-SHA512: c71c46c13ad5a6d39ae72982b7765f690e7391092e4983887a53dceeee507c8fc256e887351bbe35c051bf88d2babeb283e17a2588ee86ec9020c4ba426bfcd7
This PR bumps
vcpkgandccacheversions.Dependency changes in
vcpkg(2022.09.27 - 2023.01.09):Also see #26866 (comment).