Improve mapreduce/collectby #874
evhubAnnotations
16 errors, 7 warnings, and 4 notices
|
Python 3.4
The process '/opt/hostedtoolcache/Python/3.4.10/x64/bin/pip' failed with exit code 1
|
|
Python 2.7
Process completed with exit code 2.
|
|
Python 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 3.7
Process completed with exit code 143.
|
|
Python pypy-3.9
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.9
Process completed with exit code 143.
|
|
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
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-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 3.6
The hosted runner: GitHub Actions 9 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
Python 3.5
The hosted runner: GitHub Actions 7 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
Python pypy-2.7
Process completed with exit code 2.
|
|
Python 3.12
Process completed with exit code 2.
|
|
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/
|
|
Python 3.4
CPython version >=3.4.0 <3.5.0-0 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
CPython version >=2.7.0 <2.8.0-0 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
|
|
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
|