Skip to content

Fix CI again

Fix CI again #1739

Triggered via pull request September 30, 2024 09:16
@bloodearnestbloodearnest
synchronize #745
fix-ci2
Status Failure
Total duration 22m 28s
Artifacts

tests.yml

on: pull_request
Matrix: Run test suite
check
29s
check
Test we can build PyPI package
53s
Test we can build PyPI package
Inspect test runner output in the context of a Github Workflow
25s
Inspect test runner output in the context of a Github Workflow
Test docker image
4m 17s
Test docker image
required-checks
1s
required-checks
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 20 warnings
Run test suite (windows-2019, 3.8)
Process completed with exit code 1.
Run test suite (windows-2019, 3.10)
Process completed with exit code 1.
Run test suite (windows-2019, 3.9)
Process completed with exit code 1.
Run test suite (macos-12, 3.9)
Process completed with exit code 1.
Run test suite (macos-12, 3.8)
The hosted runner encountered an error while running your job. (Error Type: Disconnect).
required-checks
Process completed with exit code 1.
Inspect test runner output in the context of a Github Workflow
The following actions use a deprecated Node.js version and will be forced to run on node20: extractions/setup-just@69d82fb0233557aec017ef13706851d0694e0f1d. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run test suite (windows-2019, 3.8)
The following actions use a deprecated Node.js version and will be forced to run on node20: extractions/setup-just@69d82fb0233557aec017ef13706851d0694e0f1d. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run test suite (windows-2019, 3.10)
The following actions use a deprecated Node.js version and will be forced to run on node20: extractions/setup-just@69d82fb0233557aec017ef13706851d0694e0f1d. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
check
The following actions use a deprecated Node.js version and will be forced to run on node20: extractions/setup-just@69d82fb0233557aec017ef13706851d0694e0f1d. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run test suite (windows-2019, 3.9)
The following actions use a deprecated Node.js version and will be forced to run on node20: extractions/setup-just@69d82fb0233557aec017ef13706851d0694e0f1d. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test we can build PyPI package
The following actions use a deprecated Node.js version and will be forced to run on node20: extractions/setup-just@69d82fb0233557aec017ef13706851d0694e0f1d. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run test suite (ubuntu-22.04, 3.10)
The following actions use a deprecated Node.js version and will be forced to run on node20: extractions/setup-just@69d82fb0233557aec017ef13706851d0694e0f1d. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run test suite (ubuntu-22.04, 3.8)
The following actions use a deprecated Node.js version and will be forced to run on node20: extractions/setup-just@69d82fb0233557aec017ef13706851d0694e0f1d. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run test suite (ubuntu-20.04, 3.8)
The following actions use a deprecated Node.js version and will be forced to run on node20: extractions/setup-just@69d82fb0233557aec017ef13706851d0694e0f1d. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run test suite (ubuntu-22.04, 3.9)
The following actions use a deprecated Node.js version and will be forced to run on node20: extractions/setup-just@69d82fb0233557aec017ef13706851d0694e0f1d. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run test suite (ubuntu-20.04, 3.10)
The following actions use a deprecated Node.js version and will be forced to run on node20: extractions/setup-just@69d82fb0233557aec017ef13706851d0694e0f1d. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test docker image
The following actions use a deprecated Node.js version and will be forced to run on node20: extractions/setup-just@69d82fb0233557aec017ef13706851d0694e0f1d. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run test suite (ubuntu-20.04, 3.9)
The following actions use a deprecated Node.js version and will be forced to run on node20: extractions/setup-just@69d82fb0233557aec017ef13706851d0694e0f1d. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run test suite (macos-12, 3.10)
The following actions use a deprecated Node.js version and will be forced to run on node20: extractions/setup-just@69d82fb0233557aec017ef13706851d0694e0f1d. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run test suite (macos-12, 3.10)
Treating docker as a formula. For the cask, use homebrew/cask/docker or specify the `--cask` flag. To silence this message, use the `--formula` flag.
Run test suite (macos-12, 3.10)
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.
Run test suite (macos-12, 3.9)
Treating docker as a formula. For the cask, use homebrew/cask/docker or specify the `--cask` flag. To silence this message, use the `--formula` flag.
Run test suite (macos-12, 3.9)
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.
Run test suite (macos-12, 3.8)
Treating docker as a formula. For the cask, use homebrew/cask/docker or specify the `--cask` flag. To silence this message, use the `--formula` flag.
Run test suite (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.