Skip to content

Add geometry type CompoundMesh #523

Add geometry type CompoundMesh

Add geometry type CompoundMesh #523

Triggered via pull request September 19, 2024 15:47
Status Failure
Total duration 2m 7s
Artifacts

mac.yml

on: pull_request
Matrix: build-macos
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 14 warnings
build-macos (macos-14, arm64-osx-dynamic-release, arm64, /opt/homebrew)
Process completed with exit code 1.
build-macos (macos-12, x64-osx-dynamic-release, x64, /usr/local)
Process completed with exit code 1.
build-macos (macos-14, arm64-osx-dynamic-release, arm64, /opt/homebrew)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build-macos (macos-14, arm64-osx-dynamic-release, arm64, /opt/homebrew)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v4, actions/checkout@v3, pat-s/always-upload-cache@v3, actions/github-script@v6. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build-macos (macos-14, arm64-osx-dynamic-release, arm64, /opt/homebrew)
Treating cmake as a formula. For the cask, use homebrew/cask/cmake or specify the `--cask` flag.
build-macos (macos-14, arm64-osx-dynamic-release, arm64, /opt/homebrew)
cmake 3.30.3 is already installed and up-to-date. To reinstall 3.30.3, run: brew reinstall cmake
build-macos (macos-14, arm64-osx-dynamic-release, arm64, /opt/homebrew)
gcc 14.2.0 is already installed and up-to-date. To reinstall 14.2.0, run: brew reinstall gcc
build-macos (macos-12, x64-osx-dynamic-release, x64, /usr/local)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build-macos (macos-12, x64-osx-dynamic-release, x64, /usr/local)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v4, actions/checkout@v3, pat-s/always-upload-cache@v3, actions/github-script@v6. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build-macos (macos-12, x64-osx-dynamic-release, x64, /usr/local)
Treating cmake as a formula. For the cask, use homebrew/cask/cmake or specify the `--cask` flag.
build-macos (macos-12, x64-osx-dynamic-release, x64, /usr/local)
libomp 18.1.8 is already installed and up-to-date. To reinstall 18.1.8, run: brew reinstall libomp
build-macos (macos-12, x64-osx-dynamic-release, x64, /usr/local)
cmake 3.30.3 is already installed and up-to-date. To reinstall 3.30.3, run: brew reinstall cmake
build-macos (macos-12, x64-osx-dynamic-release, x64, /usr/local)
autoconf 2.72 is already installed and up-to-date. To reinstall 2.72, run: brew reinstall autoconf
build-macos (macos-12, x64-osx-dynamic-release, x64, /usr/local)
libtool 2.4.7 is already installed and up-to-date. To reinstall 2.4.7, run: brew reinstall libtool
build-macos (macos-12, x64-osx-dynamic-release, x64, /usr/local)
gcc 14.2.0 is already installed and up-to-date. To reinstall 14.2.0, run: brew reinstall gcc
build-macos (macos-12, x64-osx-dynamic-release, x64, /usr/local)
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.