Skip to content

🐛 Fix bit_bang_i2c/spi (#44) #120

🐛 Fix bit_bang_i2c/spi (#44)

🐛 Fix bit_bang_i2c/spi (#44) #120

Triggered via push November 30, 2024 14:44
Status Success
Total duration 9m 19s
Artifacts

ci.yml

on: push
library_check  /  ...  /  lint
1m 15s
library_check / lint / lint
library_check  /  ...  /  docs
12s
library_check / docs / docs
deployment_check  /  ...  /  deploy
8m 1s
deployment_check / linux_x86_64_clang / deploy
deployment_check  /  ...  /  deploy
1m 12s
deployment_check / cortex-m0 / deploy
deployment_check  /  ...  /  deploy
1m 13s
deployment_check / cortex-m0plus / deploy
deployment_check  /  ...  /  deploy
1m 18s
deployment_check / cortex-m1 / deploy
deployment_check  /  ...  /  deploy
1m 11s
deployment_check / cortex-m3 / deploy
deployment_check  /  ...  /  deploy
1m 14s
deployment_check / cortex-m4 / deploy
deployment_check  /  ...  /  deploy
1m 13s
deployment_check / cortex-m4f / deploy
Matrix: library_check / tests / run_tests
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
library_check / tests / run_tests (macos-12, brew install llvm@17 && sudo ln -s $(brew --prefix llvm)/bin/clang-tidy /usr...
The macOS-12 environment is deprecated, consider switching to macOS-13, macOS-14 (macos-latest) or macOS-15. For more details, see https://github.com/actions/runner-images/issues/10721
library_check / tests / run_tests (macos-12, brew install llvm@17 && sudo ln -s $(brew --prefix llvm)/bin/clang-tidy /usr...
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.