Test

Fix registry for `min` in buitlins #105

Triggered via pull request September 16, 2024 21:15

zm711

opened #242

zm711:fix-min

Status Failure

Total duration 45m 44s

Artifacts –

test.yml

on: pull_request

Matrix: test

Matrix: type-check

Annotations

20 errors and 57 warnings

test (ubuntu-latest, 3.10, 1.22)

The hosted runner: GitHub Actions 14 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.

test (ubuntu-latest, 3.10, 1.24)

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.

test (ubuntu-latest, 3.10, 1.23)

The hosted runner: GitHub Actions 12 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.

test (ubuntu-latest, 3.10, 1.26)

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.

test (ubuntu-latest, 3.10, 1.25)

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.

test (ubuntu-latest, 3.10, 2.0)

The hosted runner: GitHub Actions 13 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.

test (ubuntu-latest, 3.11, 1.22)

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.

test (ubuntu-latest, 3.11, 1.24)

The hosted runner: GitHub Actions 20 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.

test (ubuntu-latest, 3.11, 1.23)

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.

test (ubuntu-latest, 3.11, 1.25)

The hosted runner: GitHub Actions 17 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.

test (ubuntu-latest, 3.11, 1.26)

The hosted runner: GitHub Actions 1 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.

test (ubuntu-latest, 3.12, 1.26)

The hosted runner: GitHub Actions 15 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.

test (ubuntu-latest, 3.11, 2.0)

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.

test (ubuntu-latest, 3.9, 1.22)

The hosted runner: GitHub Actions 11 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.

test (ubuntu-latest, 3.9, 1.24)

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.

test (ubuntu-latest, 3.9, 1.23)

The hosted runner: GitHub Actions 16 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.

test (ubuntu-latest, 3.9, 1.25)

The hosted runner: GitHub Actions 19 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.

test (ubuntu-latest, 3.9, 1.26)

The hosted runner: GitHub Actions 18 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.

test (ubuntu-latest, 3.9, 2.0)

The hosted runner: GitHub Actions 10 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.

type-check (ubuntu-latest, 3.10, 1.22)

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.

type-check (ubuntu-latest, 3.9, 1.26)

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

type-check (ubuntu-latest, 3.9, 1.26)

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

type-check (ubuntu-latest, 3.9, 1.26)

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/

type-check (ubuntu-latest, 3.10, 1.23)