Skip to content

Fixes #430: Validate an artifact using "hash" rather than "fileName" #46

Fixes #430: Validate an artifact using "hash" rather than "fileName"

Fixes #430: Validate an artifact using "hash" rather than "fileName" #46

Triggered via pull request December 12, 2023 10:52
Status Failure
Total duration 53m 30s
Artifacts

python-package.yml

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

Annotations

8 errors and 16 warnings
build (3.10, latest)
The hosted runner: GitHub Actions 3 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.
build (3.10, stable)
The hosted runner: GitHub Actions 2 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.
build (3.11, stable)
The hosted runner: GitHub Actions 4 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.
build (3.8, latest)
The hosted runner: GitHub Actions 6 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.
build (3.11, latest)
The hosted runner: GitHub Actions 5 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.
build (3.9, latest)
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.
build (3.8, stable)
The hosted runner: GitHub Actions 8 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.
build (3.9, stable)
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.
build (3.10, latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build (3.10, latest)
Failed to restore: getCacheEntry failed: connect ECONNREFUSED 54.185.253.63:443
build (3.10, stable)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build (3.10, stable)
Failed to restore: getCacheEntry failed: connect ECONNREFUSED 54.185.253.63:443
build (3.11, stable)
Failed to restore: getCacheEntry failed: connect ECONNREFUSED 54.185.253.63:443
build (3.11, stable)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build (3.8, latest)
Failed to restore: getCacheEntry failed: connect ECONNREFUSED 54.185.253.63:443
build (3.8, latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build (3.11, latest)
Failed to restore: getCacheEntry failed: connect ECONNREFUSED 54.185.253.63:443
build (3.11, latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build (3.9, latest)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build (3.9, latest)
Failed to restore: getCacheEntry failed: connect ECONNREFUSED 54.185.253.63:443
build (3.8, stable)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build (3.8, stable)
Failed to restore: getCacheEntry failed: connect ECONNREFUSED 54.185.253.63:443
build (3.9, stable)
Failed to restore: getCacheEntry failed: connect ECONNREFUSED 54.185.253.63:443
build (3.9, stable)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/