Skip to content

MacOS_CI

MacOS_CI #1342

Triggered via schedule October 6, 2024 07:17
Status Queued
Total duration
Artifacts

macos.yml

on: schedule
big_sur_build_and_test
big_sur_build_and_test
monterey_build_and_test
13m 14s
monterey_build_and_test
ventura_build_and_test
1m 16s
ventura_build_and_test
big_sur_ubsan
big_sur_ubsan
big_sur_asan
big_sur_asan
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
ventura_build_and_test
Process completed with exit code 1.
monterey_build_and_test
Process completed with exit code 1.
monterey_build_and_test
Failed applying an ad-hoc signature to /usr/local/Cellar/openjdk@21/21.0.4/libexec/openjdk.jdk/Contents/MacOS/libjli.dylib: /usr/local/Cellar/openjdk@21/21.0.4/libexec/openjdk.jdk/Contents/MacOS/libjli.dylib: replacing existing signature /usr/local/Cellar/openjdk@21/21.0.4/libexec/openjdk.jdk/Contents/MacOS/libjli.dylib: resource fork, Finder information, or similar detritus not allowed
ventura_build_and_test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
monterey_build_and_test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
monterey_build_and_test
You are using macOS 12. We (and Apple) do not provide support for this old version. It is expected behaviour that some formulae will fail to build in this old version. It is expected behaviour that Homebrew will be buggy and slow. Do not create any issues about this on Homebrew's GitHub repositories. Do not create any issues even if you think this message is unrelated. Any opened issues will be immediately closed without response. Do not ask for help from Homebrew or its maintainers on social media. You may ask for help in Homebrew's discussions but are unlikely to receive a response. Try to figure out the problem yourself and submit a fix as a pull request. We will review it but may or may not accept it.