Skip to content

fix(WebSocket): properly handle HTTPStatus and HTTPError cases (#2150) #1456

fix(WebSocket): properly handle HTTPStatus and HTTPError cases (#2150)

fix(WebSocket): properly handle HTTPStatus and HTTPError cases (#2150) #1456

Triggered via push November 12, 2023 23:24
Status Failure
Total duration 5m 56s
Artifacts

tests.yaml

on: push
Matrix: run_tox
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 2 warnings
tox -e asgilook (3.10 on ubuntu-latest)
Process completed with exit code 1.
tox -e pep8 (3.10 on ubuntu-latest)
Process completed with exit code 1.
tox -e py311_cython (3.11 on ubuntu-latest)
Process completed with exit code 1.
tox -e py310_cython (3.10 on ubuntu-latest)
Process completed with exit code 1.
tox -e py310_sans_msgpack (3.10 on ubuntu-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: codecov/codecov-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
tox -e py310 (3.10 on ubuntu-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: codecov/codecov-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/