Skip to content

[WIP] Add tokenize-hotwords option #983

[WIP] Add tokenize-hotwords option

[WIP] Add tokenize-hotwords option #983

Triggered via pull request October 15, 2024 07:12
Status Failure
Total duration 44m 41s
Artifacts

test-build-wheel.yaml

on: pull_request
Matrix: test-build-wheel
Fit to window
Zoom out
Zoom in

Annotations

17 errors and 2 warnings
windows-2022 3.10
Process completed with exit code 1.
ubuntu-20.04 3.7
Process completed with exit code 1.
ubuntu-20.04 3.9
Process completed with exit code 1.
ubuntu-20.04 3.8
Process completed with exit code 1.
ubuntu-22.04 3.10
Process completed with exit code 1.
ubuntu-22.04 3.11
Process completed with exit code 1.
ubuntu-22.04 3.12
Process completed with exit code 1.
windows-2022 3.8
Process completed with exit code 1.
windows-2022 3.12
Process completed with exit code 1.
windows-2022 3.7
Process completed with exit code 1.
windows-2022 3.9
Process completed with exit code 1.
windows-2022 3.11
Process completed with exit code 1.
macos-14 3.12
Process completed with exit code 1.
macos-12 3.8
Process completed with exit code 1.
macos-13 3.11
Process completed with exit code 1.
macos-13 3.9
Process completed with exit code 1.
macos-13 3.10
Process completed with exit code 1.
macos-12 3.8
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
macos-12 3.8
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.