GH-39874: [CI][C++][Windows] Use pre-installed OpenSSL#39882
Merged
kou merged 1 commit intoapache:mainfrom Feb 1, 2024
Merged
Conversation
It seems that we can't use OpenSSL via Chocolatey.
|
|
Member
Author
|
+1 |
pitrou
approved these changes
Feb 1, 2024
|
After merging your PR, Conbench analyzed the 4 benchmarking runs that have been run so far on merge-commit 63c7c4a. 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
…39882) ### Rationale for this change It seems that we can't use OpenSSL via Chocolatey. ```text openssl v3.2.0 [Approved] openssl package files install completed. Performing other installation steps. Attempt to get headers for https://slproweb.com/download/Win64OpenSSL-3_2_0.exe failed. The remote file either doesn't exist, is unauthorized, or is forbidden for url 'https://slproweb.com/download/Win64OpenSSL-3_2_0.exe'. Exception calling "GetResponse" with "0" argument(s): "The remote server returned an error: (404) Not Found." Downloading openssl 64 bit from 'https://slproweb.com/download/Win64OpenSSL-3_2_0.exe' ERROR: The remote file either doesn't exist, is unauthorized, or is forbidden for url 'https://slproweb.com/download/Win64OpenSSL-3_2_0.exe'. Exception calling "GetResponse" with "0" argument(s): "The remote server returned an error: (404) Not Found." This package is likely not broken for licensed users - see https://docs.chocolatey.org/en-us/features/private-cdn. The install of openssl was NOT successful. Error while running 'C:\ProgramData\chocolatey\lib\openssl\tools\chocolateyinstall.ps1'. See log for details. ``` ### What changes are included in this PR? Use pre-installed OpenSSL on self-hosted GitHub runner instead. ### Are these changes tested? Yes. ### Are there any user-facing changes? No. * Closes: apache#39874 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
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
2 participants
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.
Rationale for this change
It seems that we can't use OpenSSL via Chocolatey.
What changes are included in this PR?
Use pre-installed OpenSSL on self-hosted GitHub runner instead.
Are these changes tested?
Yes.
Are there any user-facing changes?
No.