Build #21862
build.yml
on: schedule
test_build
9m 43s
Matrix: preflight / preflight-tests
Annotations
5 errors and 12 warnings
|
preflight / preflight-tests (misc)
Process completed with exit code 1.
|
|
flyctl error
failed to fetch an image or build from source: failed to create buildkit client: failed to launch VM: aborted: insufficient resources available to fulfill request: could not reserve resource for machine: insufficient memory available to fulfill request (Request ID: 01KKHFEMX3XK2YNB6VGMXCXXPZ-ord)
|
|
preflight / preflight-tests (postgres)
Process completed with exit code 1.
|
|
flyctl error
Failed to run failover: failed to wait for health checks to pass: All attempts fail:⏎#1: failed to get VM 6837241a4315d8: Get "https://api.machines.dev/v1/apps/preflight-gha-23013043057-1-2026-03-brh7ppyz/machines/6837241a4315d8": net/http: request canceled⏎#2: context deadline exceeded
|
|
preflight / preflight-tests (deploy)
Process completed with exit code 1.
|
|
preflight / preflight-tests (logs)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: superfly/flyctl-actions/setup-flyctl@master. 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/
|
|
preflight / preflight-tests (console)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: superfly/flyctl-actions/setup-flyctl@master. 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/
|
|
preflight / preflight-tests (wireguard)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: superfly/flyctl-actions/setup-flyctl@master. 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/
|
|
preflight / preflight-tests (scale)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: superfly/flyctl-actions/setup-flyctl@master. 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/
|
|
preflight / preflight-tests (volume)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: superfly/flyctl-actions/setup-flyctl@master. 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/
|
|
preflight / preflight-tests (misc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: slackapi/slack-github-action@91efab103c0de0a537f72a35f6b8cda0ee76bf0a, superfly/flyctl-actions/setup-flyctl@master. 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/
|
|
preflight / preflight-tests (tokens)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: superfly/flyctl-actions/setup-flyctl@master. 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/
|
|
preflight / preflight-tests (machine)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: superfly/flyctl-actions/setup-flyctl@master. 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/
|
|
preflight / preflight-tests (apps)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: superfly/flyctl-actions/setup-flyctl@master. 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/
|
|
preflight / preflight-tests (launch)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: superfly/flyctl-actions/setup-flyctl@master. 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/
|
|
preflight / preflight-tests (postgres)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: slackapi/slack-github-action@91efab103c0de0a537f72a35f6b8cda0ee76bf0a, superfly/flyctl-actions/setup-flyctl@master. 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/
|
|
preflight / preflight-tests (deploy)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: slackapi/slack-github-action@91efab103c0de0a537f72a35f6b8cda0ee76bf0a, superfly/flyctl-actions/setup-flyctl@master. 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 | |
|---|---|---|---|
|
flyctl
|
44.5 MB |
sha256:ba6dbd87511ceb9bef7e1e741733d90068c200632e948f83002537a46aab0587
|
|