Skip to content

E2E Test Suite against by #4706

E2E Test Suite against by

E2E Test Suite against by #4706

Triggered via schedule April 7, 2026 00:24
Status Failure
Total duration 3m 28s
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 (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-home-server / (Home Server) E2E Test Suite (sqlite, memory)
Process completed with exit code 1.
E2E / e2e-self-hosted / (Self Hosting) E2E Test Suite (grpc)
Process completed with exit code 1.
E2E / e2e-self-hosted / (Self Hosting) E2E Test Suite (http)
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 (http)
Process completed with exit code 1.
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-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-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/
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/

Artifacts

Produced during runtime
Name Size Digest
home-server-failure-logs-all-mysql-memory Expired
269 KB
sha256:1a5685a13d2e6c77db911cd55dd44a6eb14c216a016bd7c81abeaa0eb5167108
home-server-failure-logs-all-mysql-redis Expired
283 KB
sha256:55bcc099e189f941233be149bd9ff7e0a4c52bd606b505c0da01dab667ed3695
home-server-failure-logs-all-sqlite-memory Expired
263 KB
sha256:a59d9b5d59149498fdc5ff2d158400440b323226d7991f7df8b583e11566c4c4
home-server-failure-logs-all-sqlite-redis Expired
277 KB
sha256:fe01d1de464d1f00eab58782dcdb6c2aabafb4fabb459dd94b51dc722a53353f
self-hosted-failure-logs-all Expired
206 KB
sha256:7a6eb3b362cb4c3b5328b77c4e9f717b9416049921a2bb66058c470da4d401de