Skip to content
Run tests

Fix Django requirement being too strict #12

Sign in to view logs

Fix Django requirement being too strict

Fix Django requirement being too strict #12

Triggered via push August 23, 2024 10:24
@ActionbActionb
pushed ef446b4
main
Status Failure
Total duration 26s
Artifacts –

test.yml

on: push
ruff
6s
ruff
Matrix: tests
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 2 warnings
tests (3.10, 5.0)
Process completed with exit code 1.
tests (3.10, 5.1)
Process completed with exit code 1.
tests (3.9, 4.2)
The job was canceled because "_3_10_5_0" failed.
tests (3.9, 4.2)
Process completed with exit code 1.
tests (3.10, 4.2)
The job was canceled because "_3_10_5_0" failed.
tests (3.10, 4.2)
Process completed with exit code 1.
tests (3.10, 5.0)
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/
tests (3.10, 5.1)
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/