CI: Downgrade to qemu-8.2.1 #5639
test.yml
on: pull_request
Lints
1m 44s
Windows tests
4m 40s
Integration tests
9m 3s
VMNet test
10m 21s
Matrix: Colima
Matrix: Integration tests (on Linux)
Matrix: Unit tests
Matrix: Upgrade test
Matrix: vz
Annotations
3 errors and 9 warnings
Upgrade test (v0.15.1)
The `brew link` step did not complete successfully
|
Upgrade test (v0.15.1)
Could not symlink share/qemu/QEMU,cgthree.bin
Target /usr/local/share/qemu/QEMU,cgthree.bin
is a symlink belonging to qemu. You can unlink it:
brew unlink qemu
To force the link and overwrite all conflicting files:
brew link --overwrite qemu
To list all files that would be deleted:
brew link --overwrite qemu --dry-run
|
Upgrade test (v0.15.1)
Process completed with exit code 1.
|
Integration tests
curl 8.10.0 is already installed and up-to-date.
To reinstall 8.10.0, run:
brew reinstall curl
|
Integration tests
jq 1.7.1 is already installed and up-to-date.
To reinstall 1.7.1, run:
brew reinstall jq
|
Integration 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.
|
VMNet test
qemu 9.1.0 is already installed and up-to-date.
To reinstall 9.1.0, run:
brew reinstall qemu
|
VMNet test
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.
|
vz (fedora.yaml)
jq 1.7.1 is already installed and up-to-date.
To reinstall 1.7.1, run:
brew reinstall jq
|
vz (default.yaml)
jq 1.7.1 is already installed and up-to-date.
To reinstall 1.7.1, run:
brew reinstall jq
|
Upgrade test (v0.15.1)
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.
|
Upgrade test (v0.15.1)
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.
|