CI_TEST

fix: return changeset items correctly from a pipeline build #42

Triggered via pull request December 9, 2023 18:15

pre-commit-ci[bot]

synchronize #850

kaltsi:changesets

Status Failure

Total duration 49m 55s

Artifacts –

python-package.yml

on: pull_request

Matrix: build

Annotations

8 errors and 16 warnings

build (3.10, latest)

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, 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 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.11, stable)

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.8, stable)

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.8, 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.9, latest)

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.11, latest)

Failed to restore: getCacheEntry failed: connect ECONNREFUSED 54.185.253.63:443

build (3.11, latest)