Skip to content

E2E Test Suite against by #4686

E2E Test Suite against by

E2E Test Suite against by #4686

Triggered via schedule March 28, 2026 00:21
Status Failure
Total duration 3m 29s
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, 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-home-server / (Home Server) E2E Test Suite (sqlite, 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-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-self-hosted / (Self Hosting) E2E Test Suite (http)
Process completed with exit code 1.
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, 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-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-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:bac9f9369165846246e44445e0837424332cc298fad12d106ac386bb6c0e8173
home-server-failure-logs-all-mysql-redis Expired
226 KB
sha256:94174495b16165c6d7eaac90cab3e3057b017c2a07ff13d3e757e8a8592c2b1f
home-server-failure-logs-all-sqlite-memory Expired
218 KB
sha256:e3ac8fa8526e54e980983b2355780faf79359a9110081e8bf3655fe979ca21ab
home-server-failure-logs-all-sqlite-redis Expired
221 KB
sha256:40493aa305e11e1b1a8f96c1fd3c57cb242eabe45488ab4ad79cf67db47f4882
self-hosted-failure-logs-all Expired
205 KB
sha256:4713380a9b2c1b7ef3965d97b9b834e0a0823c5128958d2e2476e48be2b43ca0