Skip to content

Staging CI (Batched) #69

Staging CI (Batched)

Staging CI (Batched) #69

Triggered via schedule March 25, 2026 11:29
Status Failure
Total duration 14m 14s
Artifacts 1

staging-ci.yml

on: schedule
Resolve promotion base
3s
Resolve promotion base
Check for new commits
5s
Check for new commits
Create Promotion PR
4s
Create Promotion PR
Matrix: Test Suite / tests
Matrix: Test Suite / windows-build
E2E Browser Tests  /  Build ironclaw (libsql)
2m 31s
E2E Browser Tests / Build ironclaw (libsql)
Test Suite  /  Heavy Integration Tests
4m 34s
Test Suite / Heavy Integration Tests
Test Suite  /  Telegram Channel Tests
37s
Test Suite / Telegram Channel Tests
Test Suite  /  WASM WIT Compatibility
11m 19s
Test Suite / WASM WIT Compatibility
Test Suite  /  Benchmark Compilation
8m 2s
Test Suite / Benchmark Compilation
Test Suite  /  Docker Build
13m 44s
Test Suite / Docker Build
Test Suite  /  Version Bump Check
0s
Test Suite / Version Bump Check
Matrix: E2E Browser Tests / test
Test Suite  /  Run Tests
3s
Test Suite / Run Tests
E2E Browser Tests  /  E2E Tests
3s
E2E Browser Tests / E2E Tests
Staging Gate
Staging Gate
Update staging-tested tag
Update staging-tested tag
Staging CI Summary
4s
Staging CI Summary
Fit to window
Zoom out
Zoom in

Annotations

1 error and 6 warnings
Create Promotion PR
[@octokit/auth-app] appId option is required
Create Promotion PR
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/create-github-app-token@v2. 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/
E2E Browser Tests / Build ironclaw (libsql)
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
E2E Browser Tests / E2E (core)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, actions/setup-python@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/
E2E Browser Tests / E2E (features)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, actions/setup-python@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/
E2E Browser Tests / E2E (extensions)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, actions/setup-python@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/
E2E Browser Tests / E2E (routines)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, actions/setup-python@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/

Artifacts

Produced during runtime
Name Size Digest
ironclaw-e2e-binary Expired
171 MB
sha256:beab0ad48eccddf8cb3d2e31ff9e28d50f815d4a39cea0d95584b9b9a3b3e9e6