Skip to content

E2E Test Suite against by #4710

E2E Test Suite against by

E2E Test Suite against by #4710

Triggered via schedule April 9, 2026 00:20
Status Failure
Total duration 5m 57s
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, 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 (mysql, memory)
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 (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-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 (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
4.52 MB
sha256:e23a06bccfadf3d37c768892a5ea2dfef7dc43de24ba4a828df4f82c2b3e330b
home-server-failure-logs-all-mysql-redis Expired
4.81 MB
sha256:89616f13467d6c0285baaf813537d3945c087ccf4844b7d5e74bc5754b3e0655
home-server-failure-logs-all-sqlite-memory Expired
4.65 MB
sha256:d8f96ce31174579d39956df504b20b8960d1303e1c0dceece91f121e7a472c27
home-server-failure-logs-all-sqlite-redis Expired
4.82 MB
sha256:12302a5dbce854b0b18f51bb32c7f3d1ea8293aaee5d28398ec26e695b3afab0
self-hosted-failure-logs-all Expired
2.59 MB
sha256:83d9404e8b819a57e2fdf46621ccc5f5d4ce07b7fd45aea74d36613976c751d6