libcurl build failure on macos11 and macos-latest #7945
Comments
|
I am seeing very similar problems starting this week on a totally different problem. I'm compiling with gnu fortran via mpifort for a 2 core MPI test case. It's just multi-core tests, if I compile with gfortran for a single core test case, it works great. The error I get is I have tried macos-latest, macos-11, macos-13. I have compared the mac/compiler versions and no changes since last week. I've tried to debug the issue, have gotten no where. I've run the test case on my personal iMac without any problem. This directory, /System/Library/Frameworks/Security.framework/Versions/A/Security, doesn't exist in githubActions or on my iMac, and it's never been a problem before. I have a PR into my repo to try to fix this, CICE-Consortium/CICE#847, but have no clue why this started. Was working fine for years and as recently as last week. |
|
Thanks @apcraig . Its sad that the github runners in general are pretty unstable and unreliable through new versions and this is not the first time I have been facing issues randomly popping up in unrelated portions without any relevant changes and I spend hours trying the build out via different avenues to verify if it is a valid issue or something GHA is doing. I see you are using macos-13 in the attached link. When I try with macos-13, it mostly works, with a few things I need to figure in couple build configurations. |
|
macos-13 is just the last thing I tried, normally I'm using macos-latest. |
vpolikarpov-akvelon
added
Area: C/C++
OS: macOS
investigate
|
@disa6302 , I had a quick look ato build logs, it looks like compilation takes openssl-1.0.2 and does not see EVP_PKEY (which is available in openssl-1.1.1). in curl I see that openssl dir can be passed using --with-openssl (see https://github.com/curl/curl/blob/master/.github/workflows/macos.yml) small question, does compilation work on clean macos-11 and clean macos-12 ? if so, please provide minimal repro steps. |
|
Thank you @ilia-shipitsin for the quick response. I dont see the openssl-1.0.2 being taken. And I am not sure where 1.0.2 would come from either because the system installed version is 3.x and the one being installed with the build script is 1.1.1t. I see this line in the attached build logs while trying to build libcurl.
I tried running the SDK build on a MacOS 11 and MacOS 12 EC2 instances and they run clean. It fails on macos-11 and macos-12 github action runners. For github actions, these are the steps: For steps on MacOS 12 EC2 instance: Expectation: It would run clean. |
|
thank you for the repro, I'll have a look |
|
@disa6302 , I tried to build by using your steps did I miss something ? |
|
Can you try running these exports? I need them when I run them locally but somehow do not need them on the github runner. If setting the values to these vars do not work, you can try this: |
Turns out the `curl-config` failure is related to these: - actions/runner-images#7958 - actions/runner-images#7945 Explicitly installing curl on macOS shouldn't be necessary, while on `ubuntu-latest`, we have to install `libcurl4-openssl-dev`.
Turns out the `curl-config` failure is related to these: - actions/runner-images#7958 - actions/runner-images#7945 Explicitly installing curl on macOS shouldn't be necessary, while on `ubuntu-latest`, we have to install `libcurl4-openssl-dev`.
|
is there an update on this? I am now seeing this on macos-13 as well. |
|
@disa6302 , sorry, my access to testing farm was revoked, I hope to get it back and test with updated repro steps. |
|
Thank you @ilia-shipitsin . Would appreciate if you can prioritize this. Up until day before yesterday, I was able to work around with macos13. But, now, it fails in macos13 as well with the same error (and it is strange because the version on day before yest's run was 2.307.1 as well and there has been no change in the build process since then - it could be flakiness, but will see). Runner version is 2.307.1. But the difference is in the working version, this was the set up: With the non working version it is: |
|
my access to testing farm is not something I can gain faster or not. I just can be patient. |
|
I see that you initially reported an issue against "macos-latest" which is macos-12 now. did you have successful build on macos-12 ? |
|
Right now, it does not build on any of the macos runners. As per my previous message, macos-13 fails as well and the difference seems to be in the macos version (13.4 vs 13.5). However, the build succeeds locally on all macos versions |
|
Ok. I got around the problem by running |
|
well, runners indeed may have I still cannot investigate, an access to test farm not yet restored. But it looks like you already identified the cause. |
Description
I am building a library on a github runner as part of github actions that requires building libcurl.
Libcurl version : 7.68.0
I am running this using cmake and I see this issue:
How do I fix this? I run the same thing on a Mac 11 system and a Mac 12 EC2 instance and the builds pass in those. It seems to a GHA specific issue.
For context, I did nothing to change the cmake file and the same build passed last month. The build also runs fine on MacOS 13.
Platforms affected
Runner images affected
Image version and build link
https://github.com/awslabs/amazon-kinesis-video-streams-producer-c/actions/runs/5602647587/job/15177682079
Is it regression?
2.305.0
Expected behavior
The build passes clean.
Actual behavior
The build fails
Repro steps
Try building the linked SDK on a GHA running with the build configuration.
The text was updated successfully, but these errors were encountered: