Skip to content

Migrate from buildkite to github actions. #13

Migrate from buildkite to github actions.

Migrate from buildkite to github actions. #13

Triggered via pull request March 11, 2026 22:13
Status Cancelled
Total duration 5m 48s
Artifacts

ci.yml

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

Annotations

6 errors and 29 warnings
minilints
Process completed with exit code 1.
check (windows)
Process completed with exit code 1.
format
Process completed with exit code 1.
check (macos)
Canceling since a higher priority waiting request for ci-refs/pull/4593/merge exists
check (macos)
The operation was canceled.
CI
Canceling since a higher priority waiting request for ci-refs/pull/4593/merge exists
minilints
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
check (windows)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/cache@v4, actions/checkout@v4, extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
check (windows)
Cache save failed.
format
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
format
hiding a lifetime that's elided elsewhere is confusing
format
hiding a lifetime that's elided elsewhere is confusing
format
hiding a lifetime that's elided elsewhere is confusing
format
hiding a lifetime that's elided elsewhere is confusing
format
hiding a lifetime that's elided elsewhere is confusing
format
hiding a lifetime that's elided elsewhere is confusing
format
hiding a lifetime that's elided elsewhere is confusing
format
hiding a lifetime that's elided elsewhere is confusing
format
hiding a lifetime that's elided elsewhere is confusing
format
method `setflags` is never used
check (linux)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/cache@v4, actions/checkout@v4, extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
check (linux)
Cache save failed.
check (macos)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/cache@v4, actions/checkout@v4, extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
check (macos)
Cache save failed.
check (macos)
Failed to save: "/opt/homebrew/bin/gtar" failed with error: The process '/opt/homebrew/bin/gtar' failed with exit code 1
check (macos)
hiding a lifetime that's elided elsewhere is confusing
check (macos)
hiding a lifetime that's elided elsewhere is confusing
check (macos)
hiding a lifetime that's elided elsewhere is confusing
check (macos)
hiding a lifetime that's elided elsewhere is confusing
check (macos)
hiding a lifetime that's elided elsewhere is confusing
check (macos)
hiding a lifetime that's elided elsewhere is confusing
check (macos)
hiding a lifetime that's elided elsewhere is confusing
check (macos)
hiding a lifetime that's elided elsewhere is confusing
check (macos)
hiding a lifetime that's elided elsewhere is confusing
check (macos)
hiding a lifetime that's elided elsewhere is confusing