API rate limit exceeded for 172.184.209.163. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.) - https://docs.github.com/rest/overview/resources-in-the-rest-api#rate-limiting

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

The command WITH DOCKER RUN --privileged set -e; timeout=$(expr $(date +%!s(MISSING)) + 30); docker run --name pg --network=host -d -e POSTGRES_USER=postgres -e POSTGRES_PASSWORD=postgres -e POSTGRES_DB=postgres "postgres:$POSTGRES"; while ! pg_isready --host=127.0.0.1 --port=5432 --quiet; do test "$(date +%!s(MISSING))" -le "$timeout" || (echo "timed out waiting for postgres"; exit 1); echo "waiting for postgres"; sleep 1; done; PG_URL=postgres:xxxxx@127.0.0.1 ECTO_ADAPTER=pg mix test; did not complete successfully. Exit code 1

Process completed with exit code 1.

The command WITH DOCKER RUN --privileged set -e; timeout=$(expr $(date +%!s(MISSING)) + 30); docker run --name pg --network=host -d -e POSTGRES_USER=postgres -e POSTGRES_PASSWORD=postgres -e POSTGRES_DB=postgres "postgres:$POSTGRES"; while ! pg_isready --host=127.0.0.1 --port=5432 --quiet; do test "$(date +%!s(MISSING))" -le "$timeout" || (echo "timed out waiting for postgres"; exit 1); echo "waiting for postgres"; sleep 1; done; PG_URL=postgres:xxxxx@127.0.0.1 ECTO_ADAPTER=pg mix test; did not complete successfully. Exit code 1

Process completed with exit code 1.

The command WITH DOCKER RUN --privileged set -e; timeout=$(expr $(date +%!s(MISSING)) + 30); docker run --name pg --network=host -d -e POSTGRES_USER=postgres -e POSTGRES_PASSWORD=postgres -e POSTGRES_DB=postgres "postgres:$POSTGRES"; while ! pg_isready --host=127.0.0.1 --port=5432 --quiet; do test "$(date +%!s(MISSING))" -le "$timeout" || (echo "timed out waiting for postgres"; exit 1); echo "waiting for postgres"; sleep 1; done; PG_URL=postgres:xxxxx@127.0.0.1 ECTO_ADAPTER=pg mix test; did not complete successfully. Exit code 1

Process completed with exit code 1.

The command WITH DOCKER RUN --privileged set -e; timeout=$(expr $(date +%!s(MISSING)) + 30); docker run --name pg --network=host -d -e POSTGRES_USER=postgres -e POSTGRES_PASSWORD=postgres -e POSTGRES_DB=postgres "postgres:$POSTGRES"; while ! pg_isready --host=127.0.0.1 --port=5432 --quiet; do test "$(date +%!s(MISSING))" -le "$timeout" || (echo "timed out waiting for postgres"; exit 1); echo "waiting for postgres"; sleep 1; done; PG_URL=postgres:xxxxx@127.0.0.1 ECTO_ADAPTER=pg mix test; did not complete successfully. Exit code 1

Process completed with exit code 1.

The command WITH DOCKER RUN --privileged set -e; timeout=$(expr $(date +%!s(MISSING)) + 30); docker run --name mysql --network=host -d -e MYSQL_ROOT_PASSWORD=root "mysql:$MYSQL" --sql_mode="ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION,ANSI_QUOTES" --default-authentication-plugin=mysql_native_password; while ! mysqladmin ping --host=127.0.0.1 --port=3306 --protocol=TCP --silent; do test "$(date +%!s(MISSING))" -le "$timeout" || (echo "timed out waiting for mysql"; exit 1); echo "waiting for mysql"; sleep 1; done; MYSQL_URL=root:xxxxx@127.0.0.1 ECTO_ADAPTER=myxql mix test; did not complete successfully. Exit code 1

Process completed with exit code 1.

The command WITH DOCKER RUN --privileged set -e; timeout=$(expr $(date +%!s(MISSING)) + 30); docker run --name mysql --network=host -d -e MYSQL_ROOT_PASSWORD=root "mysql:$MYSQL" --sql_mode="ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION,ANSI_QUOTES" --default-authentication-plugin=mysql_native_password; while ! mysqladmin ping --host=127.0.0.1 --port=3306 --protocol=TCP --silent; do test "$(date +%!s(MISSING))" -le "$timeout" || (echo "timed out waiting for mysql"; exit 1); echo "waiting for mysql"; sleep 1; done; MYSQL_URL=root:xxxxx@127.0.0.1 ECTO_ADAPTER=myxql mix test; did not complete successfully. Exit code 1

Process completed with exit code 1.

The command WITH DOCKER RUN --privileged set -e; timeout=$(expr $(date +%!s(MISSING)) + 30); docker run -d -p 1433:1433 --name mssql -e 'ACCEPT_EULA=Y' -e 'MSSQL_SA_PASSWORD=some!Password' "mcr.microsoft.com/mssql/server:$MSSQL-latest"; while ! sqlcmd -C -S tcp:127.0.0.1,1433 -U sa -P 'some!Password' -Q "SELECT 1" >/dev/null 2>&1; do test "$(date +%!s(MISSING))" -le "$timeout" || (echo "timed out waiting for mssql"; exit 1); echo "waiting for mssql"; sleep 1; done; ECTO_ADAPTER=tds mix test; did not complete successfully. Exit code 1

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: earthly/actions-setup@v1. 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/

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 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/

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 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/

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 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/

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>0pssgagAAAAAfLZYm0BStQZQZCsSRlq8CUEhMMzBFREdFMDQxMgBFZGdl

Failed to restore: Cache service responded with 400

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 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/

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>0qMsgagAAAADbs5Dk1SZ+QKRDlhinwBVNUEhMMzBFREdFMDExOABFZGdl

Failed to restore: Cache service responded with 400

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 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/

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>0qssgagAAAAA61wJGfJXZQrjdg7bQm/JHTEFYRURHRTE1MjAARWRnZQ==

Failed to restore: Cache service responded with 400

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 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/

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>0rssgagAAAADLszy44fz4TIHCy0ifxj56UEhYMzFFREdFMDYyMQBFZGdl

Failed to restore: Cache service responded with 400

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 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/

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>0s8sgagAAAABmatgl51oqRqw2eWgRvXFZUEhMMzBFREdFMDQxMABFZGdl

Failed to restore: Cache service responded with 400

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 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/

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>0tssgagAAAABOEtT2zmF3RrC1PnVmv5xiU0xDMzFFREdFMDIxNgBFZGdl

Failed to restore: Cache service responded with 400

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 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/

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>0ycsgagAAAAA0DPUTJZz1SayWbc1Cn3lNTVNQMzExMDAwMTA4MDQ3AEVkZ2U=