Skip to content

E2E tests

E2E tests #168

Triggered via schedule October 22, 2024 00:43
Status Success
Total duration 15m 18s
Artifacts

e2e_test.yaml

on: schedule
Matrix: e2e_tests
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
e2e_tests (macos-12)
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
e2e_tests (macos-12)
autoconf 2.72 is already installed and up-to-date. To reinstall 2.72, run: brew reinstall autoconf
e2e_tests (macos-12)
openssl@3 3.3.2 is already installed and up-to-date. To reinstall 3.3.2, run: brew reinstall openssl@3
e2e_tests (macos-12)
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.
e2e_tests (macos-12)
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.