Skip to content
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

GH-39621: [CI][Packaging] Update vcpkg to 2023.11.20 release #39622

Merged
merged 13 commits into from
Feb 6, 2024

Conversation

Tom-Newton
Copy link
Contributor

@Tom-Newton Tom-Newton commented Jan 15, 2024

Rationale for this change

Old version of vcpkg is blocking #39352

What changes are included in this PR?

  • Upgrade vcpkg
  • Fix ports patches
  • Upgrade visual studio used in windows wheel builds. VS2019 is now required for the vcpkg abseil build.
  • Move VCPKG_FORCE_SYSTEM_BINARIES to be set before vcpkg install to fix vcpkg install on linux ARM.
  • Fix for LLVM 17 which requires that an executable exports "llvm_orc_registerEHFrameSectionWrapper()" and "llvm_orc_unregisterEHFrameSectionWrapper()". This effects the java builds that depend on llvm from vcpkg for gandiva.
  • Update image used for python wheel builds on windows to 2024-02-05

Are these changes tested?

Does not change any behaviour so should be covered by existing tests

Are there any user-facing changes?

There shouldn't be

@github-actions github-actions bot added the awaiting review Awaiting review label Jan 15, 2024
@Tom-Newton
Copy link
Contributor Author

Tom-Newton commented Jan 15, 2024

The standard tests are all passing so I think at this point I need a review from someone who knows how this works 😅

@Tom-Newton Tom-Newton marked this pull request as ready for review January 15, 2024 22:42
@assignUser
Copy link
Member

@github-actions crossbow submit -g vcpkg

@kou kou changed the title GH-39621: Update vcpkg to 2023.11.20 release GH-39621: [CI][Packaging] Update vcpkg to 2023.11.20 release Jan 16, 2024
@kou
Copy link
Member

kou commented Jan 16, 2024

@github-actions crossbow submit -g wheel

Copy link

Revision: df9d5a2

Submitted crossbow builds: ursacomputing/crossbow @ actions-e1c32d09f5

Task Status
test-build-vcpkg-win GitHub Actions

Copy link

Revision: df9d5a2

Submitted crossbow builds: ursacomputing/crossbow @ actions-5775383cc3

Task Status
wheel-macos-big-sur-cp310-arm64 GitHub Actions
wheel-macos-big-sur-cp311-arm64 GitHub Actions
wheel-macos-big-sur-cp312-arm64 GitHub Actions
wheel-macos-big-sur-cp38-arm64 GitHub Actions
wheel-macos-big-sur-cp39-arm64 GitHub Actions
wheel-macos-catalina-cp310-amd64 GitHub Actions
wheel-macos-catalina-cp311-amd64 GitHub Actions
wheel-macos-catalina-cp312-amd64 GitHub Actions
wheel-macos-catalina-cp38-amd64 GitHub Actions
wheel-macos-catalina-cp39-amd64 GitHub Actions
wheel-manylinux-2-28-cp310-amd64 GitHub Actions
wheel-manylinux-2-28-cp310-arm64 GitHub Actions
wheel-manylinux-2-28-cp311-amd64 GitHub Actions
wheel-manylinux-2-28-cp311-arm64 GitHub Actions
wheel-manylinux-2-28-cp312-amd64 GitHub Actions
wheel-manylinux-2-28-cp312-arm64 GitHub Actions
wheel-manylinux-2-28-cp38-amd64 GitHub Actions
wheel-manylinux-2-28-cp38-arm64 GitHub Actions
wheel-manylinux-2-28-cp39-amd64 GitHub Actions
wheel-manylinux-2-28-cp39-arm64 GitHub Actions
wheel-manylinux-2014-cp310-amd64 GitHub Actions
wheel-manylinux-2014-cp310-arm64 GitHub Actions
wheel-manylinux-2014-cp311-amd64 GitHub Actions
wheel-manylinux-2014-cp311-arm64 GitHub Actions
wheel-manylinux-2014-cp312-amd64 GitHub Actions
wheel-manylinux-2014-cp312-arm64 GitHub Actions
wheel-manylinux-2014-cp38-amd64 GitHub Actions
wheel-manylinux-2014-cp38-arm64 GitHub Actions
wheel-manylinux-2014-cp39-amd64 GitHub Actions
wheel-manylinux-2014-cp39-arm64 GitHub Actions
wheel-windows-cp310-amd64 GitHub Actions
wheel-windows-cp311-amd64 GitHub Actions
wheel-windows-cp312-amd64 GitHub Actions
wheel-windows-cp38-amd64 GitHub Actions
wheel-windows-cp39-amd64 GitHub Actions

@Tom-Newton
Copy link
Contributor Author

Thanks for launching all the tests. I will investigate the failures

@Tom-Newton
Copy link
Contributor Author

Tom-Newton commented Jan 16, 2024

Summary of failures:
All windows builds error: building abseil:amd64-windows-static-md-release failed with: BUILD_FAILED
e.g. https://github.com/ursacomputing/crossbow/actions/runs/7535390294/job/20511298098
Failures during cmake configure. Exact failure is not obvious because it writes logs to a file that I can't open. Maybe updating to the very latest vcpkg will fix it.

Linux ARM builds Environment variable VCPKG_FORCE_SYSTEM_BINARIES must be set on arm, s390x, ppc64le and riscv platforms. e.g. https://github.com/ursacomputing/crossbow/actions/runs/7535390437/job/20511298713
Fails when installing vcpkg.

1 flake 502 Bad Gateway https://github.com/ursacomputing/crossbow/actions/runs/7535390424/job/20511298624

2 of the mac OS builds Fatal Python error: Aborted during tests at File "/Users/runner/work/crossbow/crossbow/test-amd64-env/lib/python3.11/site-packages/pyarrow/tests/test_dataset.py", line 3753 in test_parquet_dataset_lazy_filtering
e.g. https://github.com/ursacomputing/crossbow/actions/runs/7535390473/job/20511298827
I'm not really sure what this means. Is this what a segfault looks like on mac OS?

@raulcd
Copy link
Member

raulcd commented Jan 16, 2024

The macOS failures are known issues being worked on here: #39562

@raulcd
Copy link
Member

raulcd commented Jan 16, 2024

For the linux ARM failures could you try this:

diff --git a/ci/docker/python-wheel-manylinux.dockerfile b/ci/docker/python-wheel-manylinux.dockerfile
index 0a50d45..3ce3272 100644
--- a/ci/docker/python-wheel-manylinux.dockerfile
+++ b/ci/docker/python-wheel-manylinux.dockerfile
@@ -62,15 +62,16 @@ COPY ci/vcpkg/*.patch \
 COPY ci/scripts/install_vcpkg.sh \
      arrow/ci/scripts/
 ENV VCPKG_ROOT=/opt/vcpkg
-RUN arrow/ci/scripts/install_vcpkg.sh ${VCPKG_ROOT} ${vcpkg}
-ENV PATH="${PATH}:${VCPKG_ROOT}"
-
 ARG build_type=release
 ENV CMAKE_BUILD_TYPE=${build_type} \
     VCPKG_FORCE_SYSTEM_BINARIES=1 \
     VCPKG_OVERLAY_TRIPLETS=/arrow/ci/vcpkg \
     VCPKG_DEFAULT_TRIPLET=${arch_short}-linux-static-${build_type} \
     VCPKG_FEATURE_FLAGS="manifests"
+
+RUN arrow/ci/scripts/install_vcpkg.sh ${VCPKG_ROOT} ${vcpkg}
+ENV PATH="${PATH}:${VCPKG_ROOT}"
+
 COPY ci/vcpkg/vcpkg.json arrow/ci/vcpkg/
 # cannot use the S3 feature here because while aws-sdk-cpp=1.9.160 contains
 # ssl related fixes as well as we can patch the vcpkg portfile to support

Basically setting the required environment variable before installing vcpkg instead of after as we are already doing so.

@Tom-Newton
Copy link
Contributor Author

@github-actions crossbow submit -g wheel

Copy link

Only contributors can submit requests to this bot. Please ask someone from the community for help with getting the first commit in.
The Archery job run can be found at: https://github.com/apache/arrow/actions/runs/7546803265

@Tom-Newton
Copy link
Contributor Author

Tom-Newton commented Jan 16, 2024

Only contributors can submit requests to this bot. Please ask someone from the community for help with getting the first commit in.
The Archery job run can be found at: https://github.com/apache/arrow/actions/runs/7546803265

😞 It appears greater than contributor status is required.

@raulcd
Copy link
Member

raulcd commented Jan 16, 2024

@github-actions crossbow submit -g wheel

Copy link

Revision: c10f601

Submitted crossbow builds: ursacomputing/crossbow @ actions-a18c25bf37

Task Status
wheel-macos-big-sur-cp310-arm64 GitHub Actions
wheel-macos-big-sur-cp311-arm64 GitHub Actions
wheel-macos-big-sur-cp312-arm64 GitHub Actions
wheel-macos-big-sur-cp38-arm64 GitHub Actions
wheel-macos-big-sur-cp39-arm64 GitHub Actions
wheel-macos-catalina-cp310-amd64 GitHub Actions
wheel-macos-catalina-cp311-amd64 GitHub Actions
wheel-macos-catalina-cp312-amd64 GitHub Actions
wheel-macos-catalina-cp38-amd64 GitHub Actions
wheel-macos-catalina-cp39-amd64 GitHub Actions
wheel-manylinux-2-28-cp310-amd64 GitHub Actions
wheel-manylinux-2-28-cp310-arm64 GitHub Actions
wheel-manylinux-2-28-cp311-amd64 GitHub Actions
wheel-manylinux-2-28-cp311-arm64 GitHub Actions
wheel-manylinux-2-28-cp312-amd64 GitHub Actions
wheel-manylinux-2-28-cp312-arm64 GitHub Actions
wheel-manylinux-2-28-cp38-amd64 GitHub Actions
wheel-manylinux-2-28-cp38-arm64 GitHub Actions
wheel-manylinux-2-28-cp39-amd64 GitHub Actions
wheel-manylinux-2-28-cp39-arm64 GitHub Actions
wheel-manylinux-2014-cp310-amd64 GitHub Actions
wheel-manylinux-2014-cp310-arm64 GitHub Actions
wheel-manylinux-2014-cp311-amd64 GitHub Actions
wheel-manylinux-2014-cp311-arm64 GitHub Actions
wheel-manylinux-2014-cp312-amd64 GitHub Actions
wheel-manylinux-2014-cp312-arm64 GitHub Actions
wheel-manylinux-2014-cp38-amd64 GitHub Actions
wheel-manylinux-2014-cp38-arm64 GitHub Actions
wheel-manylinux-2014-cp39-amd64 GitHub Actions
wheel-manylinux-2014-cp39-arm64 GitHub Actions
wheel-windows-cp310-amd64 GitHub Actions
wheel-windows-cp311-amd64 GitHub Actions
wheel-windows-cp312-amd64 GitHub Actions
wheel-windows-cp38-amd64 GitHub Actions
wheel-windows-cp39-amd64 GitHub Actions

@Tom-Newton
Copy link
Contributor Author

I just pushed another commit to use the very latest version of vcpkg. My hope is that this will fix the windows build. (#39622 (comment) is without this update)

@raulcd

This comment was marked as outdated.

This comment was marked as outdated.

@raulcd
Copy link
Member

raulcd commented Jan 17, 2024

@github-actions crossbow submit wheel-windows-*

Copy link

Revision: 3e3bb83

Submitted crossbow builds: ursacomputing/crossbow @ actions-6216612a43

Task Status
wheel-windows-cp310-amd64 GitHub Actions
wheel-windows-cp311-amd64 GitHub Actions
wheel-windows-cp312-amd64 GitHub Actions
wheel-windows-cp38-amd64 GitHub Actions
wheel-windows-cp39-amd64 GitHub Actions

@Tom-Newton
Copy link
Contributor Author

Tom-Newton commented Jan 17, 2024

Looks like we are getting the same failures on the windows builds so will need to investigate further. Additionally the 2024-01-11 release seems to have broken the java manylinux build in the normal CI. The was working on the 2023-11-20 release so its quite tempting to go back to that.

@Tom-Newton
Copy link
Contributor Author

Tom-Newton commented Jan 21, 2024

I managed to get the windows docker build working locally. The abseil build error is

"This package requires Visual Studio 2019 (MSVC++ 16.0) or higher."

I don't know what implications are for upgrading visual studio but I will give it a try.

It also seems like windows build is broken on main though. There were lots of download failures:

error: Failed to download from mirror set
error: https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-git-9.0.0.6373.5be8fcd83-1-any.pkg.tar.zst: failed: status code 404
error: https://www2.futureware.at/~nickoe/msys2-mirror/mingw/i686/mingw-w64-i686-libwinpthread-git-9.0.0.6373.5be8fcd83-1-any.pkg.tar.zst: failed: status code 404
error: https://mirror.yandex.ru/mirrors/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-9.0.0.6373.5be8fcd83-1-any.pkg.tar.zst: failed: status code 404
error: https://mirrors.tuna.tsinghua.edu.cn/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-9.0.0.6373.5be8fcd83-1-any.pkg.tar.zst: failed: status code 404
error: https://mirrors.ustc.edu.cn/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-9.0.0.6373.5be8fcd83-1-any.pkg.tar.zst: failed: status code 404
error: https://mirror.bit.edu.cn/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-9.0.0.6373.5be8fcd83-1-any.pkg.tar.zst: WinHttpSendRequest failed with exit code 12007
error: https://mirror.bit.edu.cn/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-9.0.0.6373.5be8fcd83-1-any.pkg.tar.zst: WinHttpSendRequest failed with exit code 12007
error: https://mirror.bit.edu.cn/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-9.0.0.6373.5be8fcd83-1-any.pkg.tar.zst: WinHttpSendRequest failed with exit code 12007
error: https://mirror.bit.edu.cn/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-9.0.0.6373.5be8fcd83-1-any.pkg.tar.zst: WinHttpSendRequest failed with exit code 12007
error: https://mirror.selfnet.de/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-9.0.0.6373.5be8fcd83-1-any.pkg.tar.zst: failed: status code 404
error: https://mirrors.sjtug.sjtu.edu.cn/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-9.0.0.6373.5be8fcd83-1-any.pkg.tar.zst: failed: status code 404

Checking some of these URLs in a browser they all seem to variants of not found errors.

@Tom-Newton Tom-Newton force-pushed the tomnewton/update_vcpkg/GH-39621 branch from 8ea60d1 to 7ce22d2 Compare January 21, 2024 19:27
@kou
Copy link
Member

kou commented Jan 22, 2024

@github-actions crossbow submit wheel-windows-cp312-amd64

Copy link

Revision: 7ce22d2

Submitted crossbow builds: ursacomputing/crossbow @ actions-776e952a91

Task Status
wheel-windows-cp312-amd64 GitHub Actions

@Tom-Newton
Copy link
Contributor Author

Tom-Newton commented Feb 4, 2024

I managed to get the java builds working properly locally. Going back to the 2023.11.20 release solves one of the java errors. I'm sure all the normal CI was passing when I first opened this PR for 2023.11.20. I'm hoping it will also resolve the ARM build problems.

@Tom-Newton
Copy link
Contributor Author

Tom-Newton commented Feb 4, 2024

ARM build in normal CI seems fine now.

AMD64 Ubuntu 22.04 Java JDK 21 Maven 3.9.5 appears to be flaky. Locally is succeeds and on a previous CI run I think I saw the same error but for JDK 17 instead of 21. I'm not sure if this flakiness was created by this PR - possibly #38719 was not 100% effective. I see a few existing issues around this area but nothing obvious to indicate that the problem still exists on main. It looks like the failure is happening when trying to close the root allocator after all the child allocators have been successfully closed, so I suppose that means the leak was directly on the root allocator.

The R builds appear to be failing for the same reason as on main #39933

@kou
Copy link
Member

kou commented Feb 5, 2024

@github-actions crossbow submit java-jars

Copy link

github-actions bot commented Feb 5, 2024

Revision: 8764067

Submitted crossbow builds: ursacomputing/crossbow @ actions-a21ab902a6

Task Status
java-jars GitHub Actions

@Tom-Newton
Copy link
Contributor Author

Tom-Newton commented Feb 5, 2024

@kou please could you re-trigger archery builds. It looks like the most recent run succeeded apart from one which failed with a timeout reading from the cache https://github.com/ursacomputing/crossbow/actions/runs/7777712547/job/21206359154

@kou
Copy link
Member

kou commented Feb 5, 2024

Done! (Re-ran)

@raulcd
Copy link
Member

raulcd commented Feb 5, 2024

@github-actions crossbow submit -g wheel

Copy link

github-actions bot commented Feb 5, 2024

Revision: 8764067

Submitted crossbow builds: ursacomputing/crossbow @ actions-5e4cec918f

Task Status
wheel-macos-big-sur-cp310-arm64 GitHub Actions
wheel-macos-big-sur-cp311-arm64 GitHub Actions
wheel-macos-big-sur-cp312-arm64 GitHub Actions
wheel-macos-big-sur-cp38-arm64 GitHub Actions
wheel-macos-big-sur-cp39-arm64 GitHub Actions
wheel-macos-catalina-cp310-amd64 GitHub Actions
wheel-macos-catalina-cp311-amd64 GitHub Actions
wheel-macos-catalina-cp312-amd64 GitHub Actions
wheel-macos-catalina-cp38-amd64 GitHub Actions
wheel-macos-catalina-cp39-amd64 GitHub Actions
wheel-manylinux-2-28-cp310-amd64 GitHub Actions
wheel-manylinux-2-28-cp310-arm64 GitHub Actions
wheel-manylinux-2-28-cp311-amd64 GitHub Actions
wheel-manylinux-2-28-cp311-arm64 GitHub Actions
wheel-manylinux-2-28-cp312-amd64 GitHub Actions
wheel-manylinux-2-28-cp312-arm64 GitHub Actions
wheel-manylinux-2-28-cp38-amd64 GitHub Actions
wheel-manylinux-2-28-cp38-arm64 GitHub Actions
wheel-manylinux-2-28-cp39-amd64 GitHub Actions
wheel-manylinux-2-28-cp39-arm64 GitHub Actions
wheel-manylinux-2014-cp310-amd64 GitHub Actions
wheel-manylinux-2014-cp310-arm64 GitHub Actions
wheel-manylinux-2014-cp311-amd64 GitHub Actions
wheel-manylinux-2014-cp311-arm64 GitHub Actions
wheel-manylinux-2014-cp312-amd64 GitHub Actions
wheel-manylinux-2014-cp312-arm64 GitHub Actions
wheel-manylinux-2014-cp38-amd64 GitHub Actions
wheel-manylinux-2014-cp38-arm64 GitHub Actions
wheel-manylinux-2014-cp39-amd64 GitHub Actions
wheel-manylinux-2014-cp39-arm64 GitHub Actions
wheel-windows-cp310-amd64 GitHub Actions
wheel-windows-cp311-amd64 GitHub Actions
wheel-windows-cp312-amd64 GitHub Actions
wheel-windows-cp38-amd64 GitHub Actions
wheel-windows-cp39-amd64 GitHub Actions

Copy link
Member

@raulcd raulcd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot for the effort @Tom-Newton !
Just a minor nit but if the latest jobs are successful I think this is ready to get merged. Unless @kou has any other comment.

.env Outdated Show resolved Hide resolved
@github-actions github-actions bot added awaiting changes Awaiting changes awaiting review Awaiting review and removed awaiting review Awaiting review labels Feb 5, 2024
@raulcd
Copy link
Member

raulcd commented Feb 5, 2024

The manylinux_2_28 failures are unrelated and I've created and issue and a PR to fix them: #39943

Co-authored-by: Raúl Cumplido <raulcumplido@gmail.com>
@github-actions github-actions bot added awaiting review Awaiting review awaiting committer review Awaiting committer review and removed awaiting review Awaiting review awaiting changes Awaiting changes labels Feb 5, 2024
Copy link
Member

@kou kou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

Thanks!

@kou kou merged commit 1552510 into apache:main Feb 6, 2024
55 of 57 checks passed
@kou kou removed the awaiting committer review Awaiting committer review label Feb 6, 2024
@github-actions github-actions bot added the awaiting merge Awaiting merge label Feb 6, 2024
Copy link

After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit 1552510.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details.

dgreiss pushed a commit to dgreiss/arrow that referenced this pull request Feb 19, 2024
…pache#39622)

### Rationale for this change
Old version of vcpkg is blocking apache#39352

### What changes are included in this PR?
- Upgrade vcpkg 
- Fix ports patches
- Upgrade visual studio used in windows wheel builds. VS2019 is now required for the vcpkg `abseil` build. 
- Move `VCPKG_FORCE_SYSTEM_BINARIES` to be set before vcpkg install to fix vcpkg install on linux ARM. 
- Fix for LLVM 17 which requires that an executable exports "llvm_orc_registerEHFrameSectionWrapper()" and "llvm_orc_unregisterEHFrameSectionWrapper()". This effects the java builds that depend on llvm from vcpkg for gandiva. 
- Update image used for python wheel builds on windows to 2024-02-05

### Are these changes tested?
Does not change any behaviour so should be covered by existing tests

### Are there any user-facing changes?
There shouldn't be
* Closes: apache#39621

Lead-authored-by: Thomas Newton <thomas.w.newton@gmail.com>
Co-authored-by: Sutou Kouhei <kou@cozmixng.org>
Co-authored-by: Raúl Cumplido <raulcumplido@gmail.com>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
zanmato1984 pushed a commit to zanmato1984/arrow that referenced this pull request Feb 28, 2024
…pache#39622)

### Rationale for this change
Old version of vcpkg is blocking apache#39352

### What changes are included in this PR?
- Upgrade vcpkg 
- Fix ports patches
- Upgrade visual studio used in windows wheel builds. VS2019 is now required for the vcpkg `abseil` build. 
- Move `VCPKG_FORCE_SYSTEM_BINARIES` to be set before vcpkg install to fix vcpkg install on linux ARM. 
- Fix for LLVM 17 which requires that an executable exports "llvm_orc_registerEHFrameSectionWrapper()" and "llvm_orc_unregisterEHFrameSectionWrapper()". This effects the java builds that depend on llvm from vcpkg for gandiva. 
- Update image used for python wheel builds on windows to 2024-02-05

### Are these changes tested?
Does not change any behaviour so should be covered by existing tests

### Are there any user-facing changes?
There shouldn't be
* Closes: apache#39621

Lead-authored-by: Thomas Newton <thomas.w.newton@gmail.com>
Co-authored-by: Sutou Kouhei <kou@cozmixng.org>
Co-authored-by: Raúl Cumplido <raulcumplido@gmail.com>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
thisisnic pushed a commit to thisisnic/arrow that referenced this pull request Mar 8, 2024
…pache#39622)

### Rationale for this change
Old version of vcpkg is blocking apache#39352

### What changes are included in this PR?
- Upgrade vcpkg 
- Fix ports patches
- Upgrade visual studio used in windows wheel builds. VS2019 is now required for the vcpkg `abseil` build. 
- Move `VCPKG_FORCE_SYSTEM_BINARIES` to be set before vcpkg install to fix vcpkg install on linux ARM. 
- Fix for LLVM 17 which requires that an executable exports "llvm_orc_registerEHFrameSectionWrapper()" and "llvm_orc_unregisterEHFrameSectionWrapper()". This effects the java builds that depend on llvm from vcpkg for gandiva. 
- Update image used for python wheel builds on windows to 2024-02-05

### Are these changes tested?
Does not change any behaviour so should be covered by existing tests

### Are there any user-facing changes?
There shouldn't be
* Closes: apache#39621

Lead-authored-by: Thomas Newton <thomas.w.newton@gmail.com>
Co-authored-by: Sutou Kouhei <kou@cozmixng.org>
Co-authored-by: Raúl Cumplido <raulcumplido@gmail.com>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[CI][Packaging] Upgrade vcpkg version used for release builds
4 participants