Skip to content

Not require explicitly set ordering in DjangoConnectionField #1312

Not require explicitly set ordering in DjangoConnectionField

Not require explicitly set ordering in DjangoConnectionField #1312

Triggered via pull request April 11, 2024 13:59
Status Failure
Total duration 51s
Artifacts

tests.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 2 warnings
build (4.2, 3.8)
Process completed with exit code 1.
build (3.2, 3.10)
Process completed with exit code 1.
build (3.2, 3.8)
The job was canceled because "_3_2_3_10" failed.
build (3.2, 3.8)
Process completed with exit code 1.
build (3.2, 3.9)
The job was canceled because "_3_2_3_10" failed.
build (3.2, 3.9)
The operation was canceled.
build (4.2, 3.8)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-python@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build (3.2, 3.10)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-python@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.