Skip to content

BUG/MEDIUM: queue: make sure never to queue when there's no more serv… #1445

BUG/MEDIUM: queue: make sure never to queue when there's no more serv…

BUG/MEDIUM: queue: make sure never to queue when there's no more serv… #1445

Triggered via push November 9, 2024 06:25
Status Success
Total duration 5m 25s
Artifacts

vtest.yml

on: push
Generate Build Matrix
3s
Generate Build Matrix
Matrix: Test
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
macos-12, clang, no features
A brownout will take place on November 11, 14:00 UTC - November 12, 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
macos-12, clang, no features
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.
macos-12, clang, no features
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.