Skip to content

feat: Add get_progress and set_progress to redis result backend #164

feat: Add get_progress and set_progress to redis result backend

feat: Add get_progress and set_progress to redis result backend #164

Re-run triggered August 18, 2024 08:28
Status Failure
Total duration 2m 45s
Artifacts

test.yml

on: pull_request
Matrix: lint
Matrix: pytest
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 3 warnings
pytest (3.9)
Process completed with exit code 127.
pytest (3.11)
The job was canceled because "_3_9" failed.
pytest (3.11)
Process completed with exit code 127.
pytest (3.8)
The job was canceled because "_3_9" failed.
pytest (3.8)
Process completed with exit code 127.
pytest (3.12)
The job was canceled because "_3_9" failed.
pytest (3.12)
Process completed with exit code 127.
pytest (3.10)
The job was canceled because "_3_9" failed.
pytest (3.10)
Process completed with exit code 127.
lint (ruff)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
lint (mypy)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
lint (black)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/