-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
cURL fails in the latest mac 12.7.4 and 14.4.1 runner releases #9626
Comments
FWIW the same problem happened on macOS12 too. |
Example of failing macOS 12 build below. Note that we upgraded this runner to macOS-13 as a temporary fix which worked, but macOS-14 started failing today when those images updated. https://github.com/denoland/deno/actions/runs/8529068224/job/23364054712
Same error:
|
Might be related to #9586 |
@erik-bershel Unfortunately this appears to be caused by #9586. It looks like we're preferentially binding ipv6, so curl can no longer connect to our localhost address with the |
Hey @mmastrac! |
Thanks @erik-bershel! Appreciate it 😀 |
actions/runner-images#9626 Signed-off-by: Andrew Haines <haines@cerbos.dev>
Hey there! |
See actions/runner-images#9626 for more information
Description
Hi all,
For some strange reason, our mac arm64 CI started failing as soon as the runners ticked over to 14.4.1.
It appears that cURL is unable to connect to a localhost or local unix socket for a server that is certainly running at the time.
Example failed run: https://github.com/denoland/deno/actions/runs/8544295631/job/23410919147?pr=23212
Actual output from cURL:
Build info:
Platforms affected
Runner images affected
Image version and build link
20240402.2
https://github.com/denoland/deno/actions/runs/8544295631/job/23410919147?pr=23212
Is it regression?
Yes
Expected behavior
cURL should connect successfully (as it does on other platforms)
Actual behavior
cURL fails to connect with cURL error 7 (failed to connect)
Repro steps
The text was updated successfully, but these errors were encountered: