Skip to content

E2E Test Suite against by #4698

E2E Test Suite against by

E2E Test Suite against by #4698

Triggered via schedule April 3, 2026 00:24
Status Failure
Total duration 3m 42s
Artifacts 5

e2e-test-suite.yml

on: schedule
Matrix: E2E / e2e-home-server / (Home Server) E2E Test Suite
Matrix: E2E / e2e-self-hosted / (Self Hosting) E2E Test Suite
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 6 warnings
E2E / e2e-home-server / (Home Server) E2E Test Suite (sqlite, memory)
Process completed with exit code 1.
E2E / e2e-home-server / (Home Server) E2E Test Suite (mysql, memory)
Process completed with exit code 1.
E2E / e2e-home-server / (Home Server) E2E Test Suite (mysql, redis)
Process completed with exit code 1.
E2E / e2e-home-server / (Home Server) E2E Test Suite (sqlite, redis)
Process completed with exit code 1.
E2E / e2e-self-hosted / (Self Hosting) E2E Test Suite (http)
Process completed with exit code 1.
E2E / e2e-self-hosted / (Self Hosting) E2E Test Suite (grpc)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
E2E / e2e-self-hosted / (Self Hosting) E2E Test Suite (grpc)
Process completed with exit code 1.
E2E / e2e-home-server / (Home Server) E2E Test Suite (sqlite, memory)
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-node@v4, actions/upload-artifact@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/
E2E / e2e-home-server / (Home Server) E2E Test Suite (mysql, memory)
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-node@v4, actions/upload-artifact@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/
E2E / e2e-home-server / (Home Server) E2E Test Suite (mysql, redis)
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-node@v4, actions/upload-artifact@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/
E2E / e2e-home-server / (Home Server) E2E Test Suite (sqlite, redis)
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-node@v4, actions/upload-artifact@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/
E2E / e2e-self-hosted / (Self Hosting) E2E Test Suite (http)
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-node@v4, actions/upload-artifact@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/
E2E / e2e-self-hosted / (Self Hosting) E2E Test Suite (grpc)
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-node@v4, actions/upload-artifact@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/

Artifacts

Produced during runtime
Name Size Digest
home-server-failure-logs-all-mysql-memory Expired
223 KB
sha256:c3bd7bd514f2db4b549db5ac314da9d4f025194b61c85aa89a5f5825e63820c3
home-server-failure-logs-all-mysql-redis Expired
226 KB
sha256:7dca50efa53317505f5c9bca481431db0431e242e52494ddddb115ddaaabb3bc
home-server-failure-logs-all-sqlite-memory Expired
218 KB
sha256:b5646a97b770894525a821895c638ccb305ff9a01032b344d5f0efb5e81f6c80
home-server-failure-logs-all-sqlite-redis Expired
221 KB
sha256:62db47a6a03de6c9931a97ccd6d624149acd6e4234231456623dedbe4fd4c985
self-hosted-failure-logs-all Expired
205 KB
sha256:37cbe2090e5a1cea25ef05468a4d8d55197165c9a28a8ace26b5288b2753f173