Skip to content

Run examples

Run examples #740

Triggered via schedule June 27, 2023 05:13
Status Failure
Total duration 1d 13h 36m 15s
Artifacts

main.yml

on: schedule
Check for errors using pylint
1m 23s
Check for errors using pylint
Matrix: build-examples-docs
Matrix: examples
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 4 warnings
Build examples (py3.7/windows)
Process completed with exit code 127.
Build examples (py3.8/windows)
Process completed with exit code 127.
Build examples (py3.9/windows)
Process completed with exit code 127.
Build examples docs (py3.7)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
Build examples (py3.7/linux)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
Build examples docs (py3.8)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
Build examples (py3.9/linux)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
Build examples docs (py3.9)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
Build examples (py3.8/linux)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
Build examples (py3.7/windows)
No files were found with the provided path: ci-test-errors.txt. No artifacts will be uploaded.
Build examples (py3.8/windows)
No files were found with the provided path: ci-test-errors.txt. No artifacts will be uploaded.
Build examples (py3.9/windows)
No files were found with the provided path: ci-test-errors.txt. No artifacts will be uploaded.
Run examples
The ubuntu-18.04 environment is deprecated, consider switching to ubuntu-20.04(ubuntu-latest), or ubuntu-22.04 instead. For more details see https://github.com/actions/virtual-environments/issues/6002