Skip to content

✅ CI

✅ CI #79

Triggered via schedule October 13, 2024 12:12
Status Failure
Total duration 2m 8s
Artifacts

ci.yml

on: schedule
ci  /  ...  /  lint
21s
ci  /  ...  /  docs
10s
deploy_all_check  /  ...  /  deploy
1m 8s
deploy_all_check  /  ...  /  deploy
1m 12s
deploy_all_check  /  ...  /  deploy
1m 13s
deploy_all_check  /  ...  /  deploy
1m 25s
deploy_all_check  /  ...  /  deploy
1m 15s
deploy_all_check  /  ...  /  deploy
1m 34s
deploy_all_check  /  ...  /  deploy
1m 9s
demo_check_lpc4074  /  build
21s
demo_check_lpc4078  /  build
29s
demo_check_stm32f103c8  /  build
21s
demo_check_mod-stm32f1-v4  /  build
29s
demo_check_mod-lpc40-v5  /  build
19s
Matrix: ci / tests / run_tests

Annotations

5 errors and 2 warnings
demo_check_stm32f103c8 / build
Process completed with exit code 1.
demo_check_lpc4074 / build
Process completed with exit code 1.
demo_check_mod-lpc40-v5 / build
Process completed with exit code 1.
demo_check_lpc4078 / build
Process completed with exit code 1.
demo_check_mod-stm32f1-v4 / build
Process completed with exit code 1.
ci / tests / run_tests (macos-12, brew install llvm@17 && sudo ln -s $(brew --prefix llvm)/bin/clang-tidy /usr...
A brownout will take place on November 4, 14:00 UTC - November 5, 00:00 UTC to raise awareness of the upcoming macOS-12 environment removal. For more details, see https://github.com/actions/runner-images/issues/10721
ci / 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.