Skip to content

Fix docs, tests

Fix docs, tests #846

Triggered via push September 23, 2023 08:27
Status Failure
Total duration 6h 0m 25s
Artifacts

run-tests.yml

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

Annotations

13 errors, 9 warnings, and 4 notices
Python pypy-3.9
Process completed with exit code 2.
Python 2.7
Process completed with exit code 2.
Python 3.7
Process completed with exit code 2.
Python 3.5
Process completed with exit code 2.
Python pypy-3.8
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Python pypy-3.8
The operation was canceled.
Python pypy-3.6
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Python pypy-3.6
Process completed with exit code 143.
Python pypy-3.7
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Python pypy-3.7
Process completed with exit code 143.
Python pypy-2.7
Process completed with exit code 2.
Python 3.6
The operation was canceled.
Python 3.4
The operation was canceled.
Python 2.7
CPython version 2.7.x is not supported by actions/setup-python. This probably means you are using a deprecated version. If this is not the case, you may suppress the warning setting input "allow-build" to either "info" or "allow".
Python 2.7
The support for python 2.7 will be removed on June 19. Related issue: https://github.com/actions/setup-python/issues/672
Python 3.5
CPython version 3.5.x is not supported by actions/setup-python. This probably means you are using a deprecated version. If this is not the case, you may suppress the warning setting input "allow-build" to either "info" or "allow".
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
Python 3.6
CPython version 3.6.x is not supported by actions/setup-python. This probably means you are using a deprecated version. If this is not the case, you may suppress the warning setting input "allow-build" to either "info" or "allow".
Python 3.4
CPython version 3.4.x is not supported by actions/setup-python. This probably means you are using a deprecated version. If this is not the case, you may suppress the warning setting input "allow-build" to either "info" or "allow".
Python 3.10
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
Python 3.9
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
Python 3.8
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/
Python 3.11
Using a user-provided API token for authentication against https://upload.pypi.org/legacy/