Skip to content

upgrade macos runner? #16

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

Closed
2bndy5 opened this issue May 7, 2024 · 4 comments
Closed

upgrade macos runner? #16

2bndy5 opened this issue May 7, 2024 · 4 comments

Comments

@2bndy5
Copy link

2bndy5 commented May 7, 2024


Git blame points to this PR in upstream.

According to the actions/runner-images, MacOS-11 is deprecated, and the latest is up to MacOS-14

@shenxianpeng
Copy link
Contributor

Yes let's try to upgrade macOS runner to MacOS-14 to have a look

@shenxianpeng
Copy link
Contributor

shenxianpeng commented Jun 3, 2024

I have upgraded the Macos Runner to macos-14

I am going to publish a pre-release for master-a13caef5 for testing.

@shenxianpeng
Copy link
Contributor

I tested the new pre-release master-a13caef5, the static binaries on macOS still has the problem from version 14~18.

dyld[3039]: Library not loaded: /usr/local/opt/zstd/lib/libzstd.1.dylib
  Referenced from: <54D844F3-D2D4-323E-9B2B-6EC303AF4B79> /Users/runner/work/clang-tools-static-binaries/clang-tools-static-binaries/clang-format-16_macosx-amd64
  Reason: tried: '/usr/local/opt/zstd/lib/libzstd.1.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/usr/local/opt/zstd/lib/libzstd.1.dylib' (no such file), '/usr/local/opt/zstd/lib/libzstd.1.dylib' (no such file), '/usr/local/lib/libzstd.1.dylib' (no such file), '/usr/lib/libzstd.1.dylib' (no such file, not in dyld cache)
/Users/runner/work/_temp/31e31703-4e2c-489d-84ab-c0645130b52c.sh: line 5:  3039 Abort trap: 6           ./clang-format-16_macosx-amd64 --version

More details please see the test job https://github.com/cpp-linter/clang-tools-static-binaries/actions/runs/9353719255/job/25744898037#step:3:40

@shenxianpeng
Copy link
Contributor

I have created a new ticket #26 to track the failure on macOS. I think this ticket can be closed now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants