Skip to content

Don't set connection close headers when they are already set on the Response #144

Don't set connection close headers when they are already set on the Response

Don't set connection close headers when they are already set on the Response #144

Triggered via pull request March 2, 2024 10:20
Status Failure
Total duration 46s
Artifacts

ci.yml

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

Annotations

12 errors and 1 warning
tox (3.11)
Process completed with exit code 255.
tox (3.9)
The job was canceled because "_3_11" failed.
tox (3.8)
The job was canceled because "_3_11" failed.
tox (3.8)
The operation was canceled.
tox (3.12)
The job was canceled because "_3_11" failed.
tox (3.12)
The operation was canceled.
tox (3.10)
The job was canceled because "_3_11" failed.
tox (3.10)
The operation was canceled.
tox (pypy-3.10)
The job was canceled because "_3_11" failed.
tox (pypy-3.10)
The operation was canceled.
tox (pypy-3.9)
The job was canceled because "_3_11" failed.
tox (pypy-3.9)
The operation was canceled.
tox (3.11)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-python@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.