Skip to content

target/esp_riscv: clear wdt interrupt states when the target is halted #51

target/esp_riscv: clear wdt interrupt states when the target is halted

target/esp_riscv: clear wdt interrupt states when the target is halted #51

Triggered via push October 4, 2024 16:24
Status Failure
Total duration 11m 18s
Artifacts

ci_workflow.yml

on: push
Build OpenOCD  /  build-macos-x86
11m 7s
Build OpenOCD / build-macos-x86
Build OpenOCD  /  build-linux
5m 20s
Build OpenOCD / build-linux
Build OpenOCD  /  build-windows
5m 22s
Build OpenOCD / build-windows
Test OpenOCD  /  Test OpenOCD on Linux
Test OpenOCD / Test OpenOCD on Linux
Test OpenOCD  /  Test OpenOCD on MacOS
Test OpenOCD / Test OpenOCD on MacOS
Test OpenOCD  /  Test OpenOCD on Windows
Test OpenOCD / Test OpenOCD on Windows
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
Build OpenOCD / build-linux
Process completed with exit code 1.
Build OpenOCD / build-windows
Process completed with exit code 1.
Build OpenOCD / build-macos-x86
Process completed with exit code 1.
Build OpenOCD / build-macos-x86
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
Build OpenOCD / build-macos-x86
automake 1.17 is already installed and up-to-date. To reinstall 1.17, run: brew reinstall automake
Build OpenOCD / build-macos-x86
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.