Support regions in image viewer #53
Triggered via pull request
November 14, 2023 17:02
jfoster17
Status
Failure
Total duration
1h 0m 36s
Artifacts
–
ci_workflows.yml
on: pull_request
initial_checks
/
Load tox environments
7s
Matrix: initial_checks / tox
Matrix: allowed_failures / tox
Matrix: tests / tox
publish
/
Build source and wheel distribution
Annotations
10 errors
|
tests / py310-test-pyqt63 (windows-latest)
Process completed with exit code 2.
|
|
tests / py311-test-pyqt64-dev (ubuntu-latest)
Process completed with exit code 1.
|
|
allowed_failures / py311-test-pyside64-skipexitcode (ubuntu-latest)
Process completed with exit code 1.
|
|
allowed_failures / py310-test-pyside63-skipexitcode (macos-latest)
Process completed with exit code 1.
|
|
tests / py310-test-pyqt515-dev-all (ubuntu-latest)
Process completed with exit code 1.
|
|
allowed_failures / py310-test-pyqt515-all (windows-latest)
Process completed with exit code 1.
|
|
allowed_failures / py310-test-pyside64 (windows-latest)
Process completed with exit code 127.
|
|
tests / py38-test-pyqt514 (windows-latest)
The hosted runner: GitHub Actions 20 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
tests / py310-test-pyqt64 (macos-latest)
The hosted runner: GitHub Actions 11 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
tests / py38-test-pyqt514-all (macos-latest)
The hosted runner: GitHub Actions 6 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|