Skip to content

feat: WarpGrid Cloud Platform (beta launch) #139

feat: WarpGrid Cloud Platform (beta launch)

feat: WarpGrid Cloud Platform (beta launch) #139

Triggered via pull request March 15, 2026 17:31
Status Failure
Total duration 6m 32s
Artifacts

ci.yml

on: pull_request
Check & Test
6m 23s
Check & Test
Docker Build
5m 2s
Docker Build
Build & Test wasi-libc
36s
Build & Test wasi-libc
Build & Verify TinyGo
1m 31s
Build & Verify TinyGo
Build & Verify ComponentizeJS
1m 33s
Build & Verify ComponentizeJS
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 13 warnings
Build & Test wasi-libc
Process completed with exit code 1.
Docker Build
buildx failed with: runtime/asm_amd64.s:1700
Check & Test
Process completed with exit code 101.
Build & Test wasi-libc
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, bytecodealliance/actions/wasmtime/setup@v1. 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/
Build & Verify TinyGo
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-go@v5, bytecodealliance/actions/wasmtime/setup@v1. 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/
Build & Verify TinyGo
Restore cache failed: Dependencies file is not found in /home/runner/_work/warpgrid/warpgrid. Supported file pattern: go.sum
Build & Verify ComponentizeJS
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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/
Docker Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/build-push-action@v2, useblacksmith/setup-docker-builder@v1. 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/
Docker Build
Expose ID not found in state, skipping sticky disk commit
Docker Build
Not using a Blacksmith builder (current builder: default). Build metrics will not be reported.
Docker Build
Failed to setup Blacksmith builder, using local builder
Docker Build
Error during Blacksmith builder setup: grpc connection test failed: [canceled] This operation was aborted. Falling back to local builder.
Docker Build
Failed to report error to Blacksmith: Request failed with status code 401
Docker Build
Error in setupStickyDisk: grpc connection test failed: [canceled] This operation was aborted
Check & Test
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-go@v5. 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 & Test
Restore cache failed: Dependencies file is not found in /home/runner/_work/warpgrid/warpgrid. Supported file pattern: go.sum