Skip to content
CI

MySQL Load: Combine sql and exit signal in one port command #2035

Sign in to view logs

MySQL Load: Combine sql and exit signal in one port command

MySQL Load: Combine sql and exit signal in one port command #2035

Triggered via pull request April 2, 2026 13:49
@greg-rychlewskigreg-rychlewski
synchronize #724
greg-rychlewski:mysql_load_fix
Status Failure
Total duration 1m 16s
Artifacts –

ci.yml

on: pull_request
Matrix: mssql integration test
Matrix: mysql integration test
Matrix: postgres integration test
Matrix: unittest
Fit to window
Zoom out
Zoom in

Annotations

18 errors and 26 warnings
unittest (1.19.4, 26.0.1)
Process completed with exit code 1.
unittest (1.19.4, 28.0.1, lint)
Process completed with exit code 1.
mssql integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 2022)
Process completed with exit code 1.
Error: Earthfile#L38
The command RUN mix compile did not complete successfully. Exit code 1
mssql integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 2019)
Process completed with exit code 1.
Error: Earthfile#L38
The command RUN mix compile did not complete successfully. Exit code 1
mysql integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 5.7)
Process completed with exit code 1.
Error: Earthfile#L38
The command RUN mix compile did not complete successfully. Exit code 1
mysql integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 8.0)
Process completed with exit code 1.
Error: Earthfile#L38
The command RUN mix compile did not complete successfully. Exit code 1
postgres integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 16.2-alpine, 4)
Process completed with exit code 1.
Error: Earthfile#L38
The command RUN mix compile did not complete successfully. Exit code 1
postgres integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 16.2-alpine, 1)
Process completed with exit code 1.
Error: Earthfile#L38
The command RUN mix compile did not complete successfully. Exit code 1
postgres integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 9.6-alpine, 1)
Process completed with exit code 1.
Error: Earthfile#L38
The command RUN mix compile did not complete successfully. Exit code 1
postgres integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 11.11-alpine, 1)
Process completed with exit code 1.
Error: Earthfile#L38
The command RUN mix compile did not complete successfully. Exit code 1
unittest (1.19.4, 26.0.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@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/
unittest (1.19.4, 28.0.1, lint)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@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/
mssql integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 2022)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, earthly/actions-setup@v1. 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/
mssql integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 2022)
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>0BXTOaQAAAAD0Nxf+6D+pS4+ObULlge56UEhMMzBFREdFMDEyMABFZGdl
mssql integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 2022)
Failed to restore: Cache service responded with 400
mssql integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 2019)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, earthly/actions-setup@v1. 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/
mssql integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 2019)
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>0DXTOaQAAAACXqI+hz00KQIvTu0cN2IXuUEhMMzBFREdFMDEyMQBFZGdl
mssql integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 2019)
Failed to restore: Cache service responded with 400
mysql integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 5.7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, earthly/actions-setup@v1. 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/
mysql integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 5.7)
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>0EHTOaQAAAABv+0NgnW3aSLYpEmWHcrrbQ08xRURHRTIwMjEARWRnZQ==
mysql integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 5.7)
Failed to restore: Cache service responded with 400
mysql integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 8.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, earthly/actions-setup@v1. 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/
mysql integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 8.0)
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>0FHTOaQAAAAAwylkUfsqlSro0tk2ZtSuLUEFPRURHRTA2MjAARWRnZQ==
mysql integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 8.0)
Failed to restore: Cache service responded with 400
postgres integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 16.2-alpine, 4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, earthly/actions-setup@v1. 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/
postgres integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 16.2-alpine, 4)
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>0FXTOaQAAAAB7yLdy57DVQruTNMX/T0q5UEFPRURHRTA2MTQARWRnZQ==
postgres integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 16.2-alpine, 4)
Failed to restore: Cache service responded with 400
postgres integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 16.2-alpine, 1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, earthly/actions-setup@v1. 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/
postgres integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 16.2-alpine, 1)
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>0FnTOaQAAAACCWfVrWetbQol//I57LJmGUEFPRURHRTA1MTYARWRnZQ==
postgres integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 16.2-alpine, 1)
Failed to restore: Cache service responded with 400
postgres integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 9.6-alpine, 1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, earthly/actions-setup@v1. 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/
postgres integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 9.6-alpine, 1)
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>0F3TOaQAAAACnGmDWmqg0R4/vGE/ItcVrQ0hHRURHRTE5MTgARWRnZQ==
postgres integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 9.6-alpine, 1)
Failed to restore: Cache service responded with 400
postgres integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 11.11-alpine, 1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, earthly/actions-setup@v1. 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/
postgres integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 11.11-alpine, 1)
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>0GXTOaQAAAACNXWhmkLAhQrLbED8V30SaQ0hHRURHRTE5MjEARWRnZQ==
postgres integration test (1.15.6-erlang-25.3.2.6-alpine-3.18.4, 11.11-alpine, 1)
Failed to restore: Cache service responded with 400
⚡