Add bindings for recovery devices. #20041
Triggered via pull request
October 25, 2024 08:14
Status
Cancelled
Total duration
8m 20s
Artifacts
–
ci.yml
on: pull_request
dispatch
7s
Matrix: rust / test-rust-non-linux
python
/
(🐧 Linux only): 🐍 Python server tests
3m 51s
rust
/
🐧 Linux: 🦀 Rust tests
7m 1s
web
/
🌐 Web tests
7m 43s
docs
/
Build & Check documentations
⭐ CI is happy ⭐
3s
Annotations
3 errors and 3 warnings
web / 🌐 Web tests
Canceling since a higher priority waiting request for 'ci-ci-aurelia/bindings/recovery_device' exists
|
web / 🌐 Web tests
The operation was canceled.
|
⭐ CI is happy ⭐
Process completed with exit code 1.
|
rust / 🍎 macOS: 🦀 Rust tests
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.
|
rust / 🍎 macOS: 🦀 Rust tests
macOS's Gatekeeper has been disabled for this Cask
|
rust / 🍎 macOS: 🦀 Rust tests
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.
|