Skip to content

docs: add instructions for stopping Flyte sandbox #7462

docs: add instructions for stopping Flyte sandbox

docs: add instructions for stopping Flyte sandbox #7462

Re-run triggered April 14, 2026 10:04
Status Success
Total duration 15m 0s
Artifacts 5

single-binary.yml

on: pull_request
test-bootstrap
1m 6s
test-bootstrap
build-and-push-single-binary-image
6m 14s
build-and-push-single-binary-image
sandbox-bundled-functional-tests
7m 30s
sandbox-bundled-functional-tests
sandbox-bundled-offloaded-functional-tests
7m 27s
sandbox-bundled-offloaded-functional-tests
build-and-push-sandbox-bundled-image
0s
build-and-push-sandbox-bundled-image
Fit to window
Zoom out
Zoom in

Annotations

11 warnings
test-bootstrap
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, golangci/golangci-lint-action@v3. 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/
test-bootstrap
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0chHeaQAAAAAQMggLxMiqQoWvrZ7bsjD0UEFPRURHRTA2MDcARWRnZQ==
test-bootstrap
Failed to restore: Cache service responded with 400
build-and-push-single-binary-image
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/upload-artifact@v4, docker/build-push-action@v6, docker/metadata-action@v3, docker/setup-buildx-action@v2, docker/setup-qemu-action@v2. 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/
build-and-push-single-binary-image
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/
build-and-push-single-binary-image
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/
build-and-push-single-binary-image
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/
build-and-push-single-binary-image
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/
build-and-push-single-binary-image
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/
sandbox-bundled-offloaded-functional-tests
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-python@v4, docker/build-push-action@v6, docker/setup-buildx-action@v2, unionai/flytectl-setup-action@v0.0.3. 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/
sandbox-bundled-functional-tests
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-python@v4, docker/build-push-action@v6, docker/setup-buildx-action@v2, unionai/flytectl-setup-action@v0.0.3. 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/

Artifacts

Produced during runtime
Name Size Digest
flyteorg~flyte~J33YQE.dockerbuild
88.1 KB
sha256:2cb081f045204e18d206f38c4ddbd972e8b8df0f7ef1b59ee2327b7ebb079f69
flyteorg~flyte~KE3F6J.dockerbuild
67 KB
sha256:f7d74fe160ff0fa557d1f36472d9ea7dc806546cc887cb983e167ceedf0f7084
flyteorg~flyte~KK5OLF.dockerbuild
79.8 KB
sha256:f321a6d02ea85abb96f55f9b057913b498bcf0d000f61b18ea26529591dccf29
flyteorg~flyte~NHML4D.dockerbuild
67.6 KB
sha256:eb16ba36fc50bd9825c990c5960fa94f730bbb08f83b0c0ecc883fc950309de3
single-binary-image
179 MB
sha256:ee091c81399526662737f9e07243399d29e9ed80b0be9a31581da635eca821d4