Failed test found in: backend/app/build/test-results/runStandardTests/TEST-io.tolgee.api.v2.controllers.ProjectStatsControllerTest.xml Error: net.javacrumbs.jsonunit.core.internal.Opentest4jExceptionFactory$JsonAssertError: JSON documents are different:

io.tolgee.api.v2.controllers.ProjectStatsControllerTest ► returns daily activity(): backend/app/src/test/kotlin/io/tolgee/api/v2/controllers/ProjectStatsControllerTest.kt#L104

Failed test found in: backend/app/build/test-results/runStandardTests/TEST-io.tolgee.api.v2.controllers.ProjectStatsControllerTest.xml backend/app/build/test-results/runStandardTests/TEST-io.tolgee.api.v2.controllers.ProjectStatsControllerTest.xml backend/app/build/test-results/runStandardTests/TEST-io.tolgee.api.v2.controllers.ProjectStatsControllerTest.xml backend/app/build/test-results/runStandardTests/TEST-io.tolgee.api.v2.controllers.ProjectStatsControllerTest.xml Error: net.javacrumbs.jsonunit.core.internal.Opentest4jExceptionFactory$JsonAssertError: JSON documents are different:

io.tolgee.api.v2.controllers.ProjectStatsControllerTest ► returns daily activity(): backend/app/src/test/kotlin/io/tolgee/api/v2/controllers/ProjectStatsControllerTest.kt#L104

Failed Test: io.tolgee.api.v2.controllers.ProjectStatsControllerTest: returns daily activity()

io.tolgee.api.v2.controllers.ProjectStatsControllerTest: returns daily activity(): net.javacrumbs.jsonunit.core.internal.Opentest4jExceptionFactory$JsonAssertError: JSON documents are different: Different value found in node "2022-04-05", expected: <5> but was: <10>. Different value found in node "2022-04-20", expected: <2> but was: <4>. - net.javacrumbs.jsonunit.core.internal.Opentest4jExceptionFactory$JsonAssertError: JSON documents are different: Different value found in node "2022-04-05", expected: <5> but was: <10>. Different value found in node "2022-04-20", expected: <2> but was: <4>. at app//net.javacrumbs.jsonunit.core.internal.Opentest4jExceptionFactory.createException(ExceptionFactory.java:37) at app//net.javacrumbs.jsonunit.core.internal.ExceptionUtils.createException(ExceptionUtils.java:45) at app//net.javacrumbs.jsonunit.core.internal.Diff.failIfDifferent(Diff.java:617) at app//net.javacrumbs.jsonunit.assertj.JsonAssert.isEqualTo(JsonAssert.java:117) at app//io.tolgee.api.v2.controllers.ProjectStatsControllerTest.returns_daily_activity$lambda$5(ProjectStatsControllerTest.kt:104) at app//io.tolgee.fixtures.StatusExpectationsKt.andAssertThatJson$lambda$12(statusExpectations.kt:66) at app//io.tolgee.fixtures.StatusExpectationsKt.tryPrettyPrinting(statusExpectations.kt:74) at app//io.tolgee.fixtures.StatusExpectationsKt.andAssertThatJson(statusExpectations.kt:65) at app//io.tolgee.api.v2.controllers.ProjectStatsControllerTest.returns daily activity(ProjectStatsControllerTest.kt:103) at java.base@21.0.10/java.lang.reflect.Method.invoke(Method.java:580) at java.base@21.0.10/java.util.ArrayList.forEach(ArrayList.java:1596) at java.base@21.0.10/java.util.ArrayList.forEach(ArrayList.java:1596)

Failed Test: io.tolgee.api.v2.controllers.ProjectStatsControllerTest: returns daily activity()

io.tolgee.api.v2.controllers.ProjectStatsControllerTest: returns daily activity(): net.javacrumbs.jsonunit.core.internal.Opentest4jExceptionFactory$JsonAssertError: JSON documents are different: Different value found in node "2022-04-05", expected: <5> but was: <10>. Different value found in node "2022-04-20", expected: <2> but was: <3>. - net.javacrumbs.jsonunit.core.internal.Opentest4jExceptionFactory$JsonAssertError: JSON documents are different: Different value found in node "2022-04-05", expected: <5> but was: <10>. Different value found in node "2022-04-20", expected: <2> but was: <3>. at app//net.javacrumbs.jsonunit.core.internal.Opentest4jExceptionFactory.createException(ExceptionFactory.java:37) at app//net.javacrumbs.jsonunit.core.internal.ExceptionUtils.createException(ExceptionUtils.java:45) at app//net.javacrumbs.jsonunit.core.internal.Diff.failIfDifferent(Diff.java:617) at app//net.javacrumbs.jsonunit.assertj.JsonAssert.isEqualTo(JsonAssert.java:117) at app//io.tolgee.api.v2.controllers.ProjectStatsControllerTest.returns_daily_activity$lambda$5(ProjectStatsControllerTest.kt:104) at app//io.tolgee.fixtures.StatusExpectationsKt.andAssertThatJson$lambda$12(statusExpectations.kt:66) at app//io.tolgee.fixtures.StatusExpectationsKt.tryPrettyPrinting(statusExpectations.kt:74) at app//io.tolgee.fixtures.StatusExpectationsKt.andAssertThatJson(statusExpectations.kt:65) at app//io.tolgee.api.v2.controllers.ProjectStatsControllerTest.returns daily activity(ProjectStatsControllerTest.kt:103) at java.base@21.0.10/java.lang.reflect.Method.invoke(Method.java:580) at java.base@21.0.10/java.util.ArrayList.forEach(ArrayList.java:1596) at java.base@21.0.10/java.util.ArrayList.forEach(ArrayList.java:1596)

Failed Test: io.tolgee.api.v2.controllers.ProjectStatsControllerTest: returns daily activity()

io.tolgee.api.v2.controllers.ProjectStatsControllerTest: returns daily activity(): net.javacrumbs.jsonunit.core.internal.Opentest4jExceptionFactory$JsonAssertError: JSON documents are different: Different value found in node "2022-04-05", expected: <5> but was: <9>. Different value found in node "2022-04-20", expected: <2> but was: <4>. - net.javacrumbs.jsonunit.core.internal.Opentest4jExceptionFactory$JsonAssertError: JSON documents are different: Different value found in node "2022-04-05", expected: <5> but was: <9>. Different value found in node "2022-04-20", expected: <2> but was: <4>. at app//net.javacrumbs.jsonunit.core.internal.Opentest4jExceptionFactory.createException(ExceptionFactory.java:37) at app//net.javacrumbs.jsonunit.core.internal.ExceptionUtils.createException(ExceptionUtils.java:45) at app//net.javacrumbs.jsonunit.core.internal.Diff.failIfDifferent(Diff.java:617) at app//net.javacrumbs.jsonunit.assertj.JsonAssert.isEqualTo(JsonAssert.java:117) at app//io.tolgee.api.v2.controllers.ProjectStatsControllerTest.returns_daily_activity$lambda$5(ProjectStatsControllerTest.kt:104) at app//io.tolgee.fixtures.StatusExpectationsKt.andAssertThatJson$lambda$12(statusExpectations.kt:66) at app//io.tolgee.fixtures.StatusExpectationsKt.tryPrettyPrinting(statusExpectations.kt:74) at app//io.tolgee.fixtures.StatusExpectationsKt.andAssertThatJson(statusExpectations.kt:65) at app//io.tolgee.api.v2.controllers.ProjectStatsControllerTest.returns daily activity(ProjectStatsControllerTest.kt:103) at java.base@21.0.10/java.lang.reflect.Method.invoke(Method.java:580) at java.base@21.0.10/java.util.ArrayList.forEach(ArrayList.java:1596) at java.base@21.0.10/java.util.ArrayList.forEach(ArrayList.java:1596)

BT ‍🔎 (server-app:runStandardTests)

Final attempt failed. Child_process exited with error code 1

Everything passed 🎉

Process completed with exit code 1.

DataCy Check 🏷️

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 will be forced to run with Node.js 24 by default starting June 2nd, 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/

Install E2E dependencies ⬇️

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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. 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 Static Check 🪲

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

Ktlint 🪲

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-java@v4, gradle/actions/setup-gradle@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

Build frontend 🏗️

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-java@v4, actions/setup-node@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

Build backend 🏗️

Frontend static check 🪲

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

BT ‍🔎 (ktlint:test)

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/download-artifact@v4, actions/setup-java@v4, actions/setup-node@v4, actions/upload-artifact@v4, ctrf-io/github-test-reporter@v1, dorny/test-reporter@v1, gradle/actions/setup-gradle@v4, nick-fields/retry@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

BT ‍🔎 (ee-test:test)

No files found matching the pattern 'ctrf/ctrf-report.json'.. Exiting action.

BT ‍🔎 (ee-test:test)

No file matches path **/build/test-results/**/TEST-*.xml

BT ‍🔎 (ee-test:test)

No files were found with the provided path: ./**/build/reports/**/*. No artifacts will be uploaded.

BT ‍🔎 (data:test)

BT ‍🔎 (security:test)

Migration Check 🗃️

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/download-artifact@v4, actions/setup-java@v4, gradle/actions/setup-gradle@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

BT ‍🔎 (server-app:runWithoutEeTests)

Schema Check 📋

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/setup-java@v4, actions/setup-node@v4, gradle/actions/setup-gradle@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 testing ‍🔎 (15, 2)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/setup-java@v4, actions/setup-node@v4, gradle/actions/setup-gradle@v4, nick-fields/retry@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

BT ‍🔎 (server-app:runWebsocketTests)

E2E testing ‍🔎 (15, 14)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/setup-java@v4, actions/setup-node@v4, gradle/actions/setup-gradle@v4, nick-fields/retry@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 testing ‍🔎 (15, 1)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/setup-java@v4, actions/setup-node@v4, gradle/actions/setup-gradle@v4, nick-fields/retry@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 testing ‍🔎 (15, 3)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/setup-java@v4, actions/setup-node@v4, gradle/actions/setup-gradle@v4, nick-fields/retry@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 testing ‍🔎 (15, 9)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/setup-java@v4, actions/setup-node@v4, gradle/actions/setup-gradle@v4, nick-fields/retry@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 testing ‍🔎 (15, 4)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/setup-java@v4, actions/setup-node@v4, gradle/actions/setup-gradle@v4, nick-fields/retry@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 testing ‍🔎 (15, 13)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/setup-java@v4, actions/setup-node@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v4, nick-fields/retry@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 testing ‍🔎 (15, 0)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/setup-java@v4, actions/setup-node@v4, gradle/actions/setup-gradle@v4, nick-fields/retry@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 testing ‍🔎 (15, 12)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/setup-java@v4, actions/setup-node@v4, gradle/actions/setup-gradle@v4, nick-fields/retry@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 testing ‍🔎 (15, 10)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/setup-java@v4, actions/setup-node@v4, gradle/actions/setup-gradle@v4, nick-fields/retry@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

BT ‍🔎 (server-app:runContextRecreatingTests)

E2E testing ‍🔎 (15, 11)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/setup-java@v4, actions/setup-node@v4, gradle/actions/setup-gradle@v4, nick-fields/retry@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 testing ‍🔎 (15, 8)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/setup-java@v4, actions/setup-node@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v4, nick-fields/retry@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 testing ‍🔎 (15, 8)

No files were found with the provided path: ./e2e/cypress/videos/**/* ./e2e/cypress/screenshots/**/* ./e2e/server. No artifacts will be uploaded.

E2E testing ‍🔎 (15, 6)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/setup-java@v4, actions/setup-node@v4, gradle/actions/setup-gradle@v4, nick-fields/retry@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 testing ‍🔎 (15, 5)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/setup-java@v4, actions/setup-node@v4, gradle/actions/setup-gradle@v4, nick-fields/retry@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 testing ‍🔎 (15, 7)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/download-artifact@v4, actions/setup-java@v4, actions/setup-node@v4, gradle/actions/setup-gradle@v4, nick-fields/retry@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

BT ‍🔎 (server-app:runStandardTests)

Test report summary exceeded limit of 65535 bytes and will be trimmed

Artifacts

Produced during runtime

Name	Size	Digest
backend	253 MB	`sha256:2ed2e5baf741716e231fb68c3d524000b8f6b52ef2660fb7838ee8bc8bff12b0`
backend_test_reports_data_test	158 KB	`sha256:e660a4534b5a97fb2962fd7322b022e86c1ded95e6be1ef22efcc447a11bfe0a`
backend_test_reports_ktlint_test	8.01 KB	`sha256:33aa18f8b0cde9fc36c638505c042e0ea477e0dbb83dde56d99f5fd1f56efd3b`
backend_test_reports_security_test	27.3 KB	`sha256:9ff3ade1cacbceb1da599067e88239031d93a87ebb3ed1ff2bbaf071d4bc621f`
backend_test_reports_server-app_runContextRecreatingTests	281 KB	`sha256:f44c689717eb29b2ffc58eaa806084294a2cf5427f0662d333358b8cd369922b`
backend_test_reports_server-app_runStandardTests	841 KB	`sha256:25d3025f7f004c0b680abf0496360b7bf9399a1c42bacbd48e2d8a45101e6a58`
backend_test_reports_server-app_runWebsocketTests	113 KB	`sha256:3ba9cf2e80b94ddc4d21344cb732a2dfff6342dc57a9a51bd2d9c1758af5f2ce`
backend_test_reports_server-app_runWithoutEeTests	73.6 KB	`sha256:2ff9a0b2aed929ea7d0b10dac10e8a90deb6368af22933e86c0e188e614f9e00`
e2e_13	118 KB	`sha256:610300047b37dc485b06344eab5cf7a79ee4da9e01e0e441ac77cc05e5b7751a`
e2e_deps	181 MB	`sha256:2b99d16ff6d5ff3fad43b7744ce469cc9014448a0df3db1c0374f7c64b8e7051`
e2e_server_log_13	591 KB	`sha256:5946039eae5447a2982e160bc6f5c7a6e24219d778e46bac7fca375e66314d7f`
e2e_server_log_8	884 KB	`sha256:79e0a81e6f5f30805bda83a9b73e0301e8f17e8bbb74425a87d52566af248c52`
webapp	2.76 MB	`sha256:819cd1616987c8737adb629b9eafa457a337c02619410cc9f99e4d7655019d08`

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat: QA checks for translations #10983

Summary

feat: QA checks for translations #10983

Uh oh!

test.yml

Annotations

Artifacts