Skip to content

Deploy Runner Binary #35

Deploy Runner Binary

Deploy Runner Binary #35

Manually triggered June 15, 2026 05:21
Status Success
Total duration 14m 20s
Artifacts 2

deploy-runner.yml

on: workflow_dispatch
Detect runner source changes
7s
Detect runner source changes
Build C SDK (linux-x64-gnu)  /  ...  /  Load configuration
4s
Build C SDK (linux-x64-gnu) / config / Load configuration
Build C SDK (linux-x64-gnu)  /  Setup matrix
2s
Build C SDK (linux-x64-gnu) / Setup matrix
Matrix: Build C SDK (linux-x64-gnu) / build
Build C SDK (linux-x64-gnu)  /  Upload to GitHub Release
0s
Build C SDK (linux-x64-gnu) / Upload to GitHub Release
Build runner binary  /  ...  /  Load configuration
4s
Build runner binary / config / Load configuration
Build runner binary  /  Build Runner (linux-amd64)
1m 58s
Build runner binary / Build Runner (linux-amd64)
Build runner binary  /  Upload to GitHub Release
Build runner binary / Upload to GitHub Release
Deploy runner to Tokyo EC2 (SSH+SCP)
34s
Deploy runner to Tokyo EC2 (SSH+SCP)
Fit to window
Zoom out
Zoom in

Annotations

5 warnings and 6 notices
Build C SDK (linux-x64-gnu) / Build (linux-x64-gnu)
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/github-script@v7, actions/upload-artifact@v4, mozilla-actions/sccache-action@v0.0.9. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Build C SDK (linux-x64-gnu) / Build (linux-x64-gnu)
Failed to save: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
Build runner binary / Build Runner (linux-amd64)
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/download-artifact@v4, actions/setup-go@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Build runner binary / Build Runner (linux-amd64)
Restore cache failed: Dependencies file is not found in /home/runner/work/boxlite/boxlite. Supported file pattern: go.sum
Deploy runner to Tokyo EC2 (SSH+SCP)
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, aws-actions/configure-aws-credentials@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
sccache stats
0% - 0 hits, 0 misses, 0 errors
Deploy runner to Tokyo EC2 (SSH+SCP)
SG rule sgr-0b1c51474b39b115a revoked
Deploy runner to Tokyo EC2 (SSH+SCP)
Runner binary swap succeeded
Deploy runner to Tokyo EC2 (SSH+SCP)
expected sha256: ae3e0dad719835fcc257c5332e28d4cc8b48a6e57f187a729868578105fb62ea
Deploy runner to Tokyo EC2 (SSH+SCP)
SG rule sgr-0b1c51474b39b115a added (22/tcp from 135.232.201.247/32)
Deploy runner to Tokyo EC2 (SSH+SCP)
Runner i-0198ebab64f67b9ff @ 43.206.240.218 (SG sg-0966b9b76795c6ab8)

Artifacts

Produced during runtime
Name Size Digest
c-sdk-linux-x64-gnu
78.1 MB
sha256:097bce03826d1c1987a9d4aedaaf08193f63cd239cb0c21f46ce8177d9fe1cf9
runner-linux-amd64
58.4 MB
sha256:61397589ef60a4e506c8288aa65dbd3fa346cde50b3c212a18d23b5d2612fff4