Skip to content

E2E Test Suite against by #4692

E2E Test Suite against by

E2E Test Suite against by #4692

Triggered via schedule March 31, 2026 00:23
Status Failure
Total duration 3m 31s
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, redis)
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 (sqlite, redis)
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 (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, 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 (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 (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 (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
223 KB
sha256:8404e41ef4dd25c1c2ab422d9f31bef05746762e57006120db63abb4322bf21a
home-server-failure-logs-all-mysql-redis Expired
226 KB
sha256:5b0b9bde61a232891539ce310a7170486d604c394f4d8ee52592f7480d03e91f
home-server-failure-logs-all-sqlite-memory Expired
218 KB
sha256:5d758292f6c73ebe24f933e6ac971b8611169681cf98061a1c0c073ad12dc207
home-server-failure-logs-all-sqlite-redis Expired
221 KB
sha256:2cd4d4d1695f5defe820338b0cb0dc13bd7d3903334cff89df9bd0779d6d7669
self-hosted-failure-logs-all Expired
206 KB
sha256:5bddbb3d08fc7ffbae16d646e33d03ec2c23b22f44b163dbb62ffce32e30a37e