Skip to content

feat: QA checks for translations #10981

feat: QA checks for translations

feat: QA checks for translations #10981

Triggered via pull request March 14, 2026 11:06
Status Failure
Total duration 19m 57s
Artifacts 13

test.yml

on: pull_request
Build backend 🏗️
3m 8s
Build backend 🏗️
Build frontend 🏗️
3m 3s
Build frontend 🏗️
Install E2E dependencies ⬇️
37s
Install E2E dependencies ⬇️
Frontend static check 🪲
4m 8s
Frontend static check 🪲
DataCy Check 🏷️
16s
DataCy Check 🏷️
E2E Static Check 🪲
35s
E2E Static Check 🪲
Ktlint 🪲
1m 22s
Ktlint 🪲
Matrix: BT ‍🔎
Schema Check 📋
2m 43s
Schema Check 📋
Migration Check 🗃️
2m 4s
Migration Check 🗃️
Matrix: E2E testing ‍🔎
Everything passed 🎉
3s
Everything passed 🎉
Fit to window
Zoom out
Zoom in

Annotations

25 errors and 37 warnings
BT ‍🔎 (ee-test:test)
No test report files were found
BT ‍🔎 (ee-test:test)
Final attempt failed. Child_process exited with error code 1
Migration Check 🗃️
Process completed with exit code 1.
Schema Check 📋
Process completed with exit code 1.
E2E testing ‍🔎 (15, 13)
Final attempt failed. Child_process exited with error code 1
E2E testing ‍🔎 (15, 8)
Final attempt failed. Child_process exited with error code 1
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 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 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 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 Error: net.javacrumbs.jsonunit.core.internal.Opentest4jExceptionFactory$JsonAssertError: JSON documents are different:
io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest ► complex edit modifies state(): backend/app/src/test/kotlin/io/tolgee/api/v2/controllers/v2KeyController/KeyControllerComplexEditTest.kt#L184
Failed test found in: backend/app/build/test-results/runStandardTests/TEST-io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest.xml Error: org.opentest4j.AssertionFailedError: [State for de is not TRANSLATED]
io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest ► complex edit modifies state(): backend/app/src/test/kotlin/io/tolgee/api/v2/controllers/v2KeyController/KeyControllerComplexEditTest.kt#L184
Failed test found in: backend/app/build/test-results/runStandardTests/TEST-io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest.xml backend/app/build/test-results/runStandardTests/TEST-io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest.xml Error: org.opentest4j.AssertionFailedError: [State for de is not REVIEWED]
io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest ► complex edit modifies state(): backend/app/src/test/kotlin/io/tolgee/api/v2/controllers/v2KeyController/KeyControllerComplexEditTest.kt#L184
Failed test found in: backend/app/build/test-results/runStandardTests/TEST-io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest.xml backend/app/build/test-results/runStandardTests/TEST-io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest.xml backend/app/build/test-results/runStandardTests/TEST-io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest.xml Error: org.opentest4j.AssertionFailedError: [State for cs is not REVIEWED]
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: <5>. - 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: <5>. 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: <5>. - 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: <5>. 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: <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: <8>. Different value found in node "2022-04-20", expected: <2> but was: <5>. - net.javacrumbs.jsonunit.core.internal.Opentest4jExceptionFactory$JsonAssertError: JSON documents are different: Different value found in node "2022-04-05", expected: <5> but was: <8>. Different value found in node "2022-04-20", expected: <2> but was: <5>. 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.v2KeyController.KeyControllerComplexEditTest: complex edit modifies state()
io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest: complex edit modifies state(): org.opentest4j.AssertionFailedError: [State for cs is not REVIEWED] expected: REVIEWED but was: TRANSLATED - org.opentest4j.AssertionFailedError: [State for cs is not REVIEWED] expected: REVIEWED but was: TRANSLATED at app//io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest.verifyStates$lambda$4(KeyControllerComplexEditTest.kt:184) at app//io.tolgee.util.TransactionUtilKt.executeInNewTransaction$lambda$0(transactionUtil.kt:24) at app//org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:140) at app//io.tolgee.util.TransactionUtilKt.executeInNewTransaction(transactionUtil.kt:23) at app//io.tolgee.util.TransactionUtilKt.executeInNewTransaction$default(transactionUtil.kt:11) at app//io.tolgee.AbstractSpringTest.executeInNewTransaction(AbstractSpringTest.kt:263) at app//io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest.verifyStates(KeyControllerComplexEditTest.kt:177) at app//io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest.doUpdateAndVerifyStates(KeyControllerComplexEditTest.kt:173) at app//io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest.complex edit modifies state(KeyControllerComplexEditTest.kt:118) 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.v2KeyController.KeyControllerComplexEditTest: complex edit modifies state()
io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest: complex edit modifies state(): org.opentest4j.AssertionFailedError: [State for cs is not REVIEWED] expected: REVIEWED but was: TRANSLATED - org.opentest4j.AssertionFailedError: [State for cs is not REVIEWED] expected: REVIEWED but was: TRANSLATED at app//io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest.verifyStates$lambda$4(KeyControllerComplexEditTest.kt:184) at app//io.tolgee.util.TransactionUtilKt.executeInNewTransaction$lambda$0(transactionUtil.kt:24) at app//org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:140) at app//io.tolgee.util.TransactionUtilKt.executeInNewTransaction(transactionUtil.kt:23) at app//io.tolgee.util.TransactionUtilKt.executeInNewTransaction$default(transactionUtil.kt:11) at app//io.tolgee.AbstractSpringTest.executeInNewTransaction(AbstractSpringTest.kt:263) at app//io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest.verifyStates(KeyControllerComplexEditTest.kt:177) at app//io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest.doUpdateAndVerifyStates(KeyControllerComplexEditTest.kt:173) at app//io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest.complex edit modifies state(KeyControllerComplexEditTest.kt:118) 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.v2KeyController.KeyControllerComplexEditTest: complex edit modifies state()
io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest: complex edit modifies state(): org.opentest4j.AssertionFailedError: [State for de is not REVIEWED] expected: REVIEWED but was: TRANSLATED - org.opentest4j.AssertionFailedError: [State for de is not REVIEWED] expected: REVIEWED but was: TRANSLATED at app//io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest.verifyStates$lambda$4(KeyControllerComplexEditTest.kt:184) at app//io.tolgee.util.TransactionUtilKt.executeInNewTransaction$lambda$0(transactionUtil.kt:24) at app//org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:140) at app//io.tolgee.util.TransactionUtilKt.executeInNewTransaction(transactionUtil.kt:23) at app//io.tolgee.util.TransactionUtilKt.executeInNewTransaction$default(transactionUtil.kt:11) at app//io.tolgee.AbstractSpringTest.executeInNewTransaction(AbstractSpringTest.kt:263) at app//io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest.verifyStates(KeyControllerComplexEditTest.kt:177) at app//io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest.doUpdateAndVerifyStates(KeyControllerComplexEditTest.kt:173) at app//io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest.complex edit modifies state(KeyControllerComplexEditTest.kt:101) 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.v2KeyController.KeyControllerComplexEditTest: complex edit modifies state()
io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest: complex edit modifies state(): org.opentest4j.AssertionFailedError: [State for cs is not REVIEWED] expected: REVIEWED but was: TRANSLATED - org.opentest4j.AssertionFailedError: [State for cs is not REVIEWED] expected: REVIEWED but was: TRANSLATED at app//io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest.verifyStates$lambda$4(KeyControllerComplexEditTest.kt:184) at app//io.tolgee.util.TransactionUtilKt.executeInNewTransaction$lambda$0(transactionUtil.kt:24) at app//org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:140) at app//io.tolgee.util.TransactionUtilKt.executeInNewTransaction(transactionUtil.kt:23) at app//io.tolgee.util.TransactionUtilKt.executeInNewTransaction$default(transactionUtil.kt:11) at app//io.tolgee.AbstractSpringTest.executeInNewTransaction(AbstractSpringTest.kt:263) at app//io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest.verifyStates(KeyControllerComplexEditTest.kt:177) at app//io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest.doUpdateAndVerifyStates(KeyControllerComplexEditTest.kt:173) at app//io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest.complex edit modifies state(KeyControllerComplexEditTest.kt:118) 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.v2KeyController.KeyControllerComplexEditTest: complex edit modifies state()
io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest: complex edit modifies state(): org.opentest4j.AssertionFailedError: [State for de is not REVIEWED] expected: REVIEWED but was: TRANSLATED - org.opentest4j.AssertionFailedError: [State for de is not REVIEWED] expected: REVIEWED but was: TRANSLATED at app//io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest.verifyStates$lambda$4(KeyControllerComplexEditTest.kt:184) at app//io.tolgee.util.TransactionUtilKt.executeInNewTransaction$lambda$0(transactionUtil.kt:24) at app//org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:140) at app//io.tolgee.util.TransactionUtilKt.executeInNewTransaction(transactionUtil.kt:23) at app//io.tolgee.util.TransactionUtilKt.executeInNewTransaction$default(transactionUtil.kt:11) at app//io.tolgee.AbstractSpringTest.executeInNewTransaction(AbstractSpringTest.kt:263) at app//io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest.verifyStates(KeyControllerComplexEditTest.kt:177) at app//io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest.doUpdateAndVerifyStates(KeyControllerComplexEditTest.kt:173) at app//io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest.complex edit modifies state(KeyControllerComplexEditTest.kt:101) 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.v2KeyController.KeyControllerComplexEditTest: complex edit modifies state()
io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest: complex edit modifies state(): org.opentest4j.AssertionFailedError: [State for de is not TRANSLATED] expected: TRANSLATED but was: REVIEWED - org.opentest4j.AssertionFailedError: [State for de is not TRANSLATED] expected: TRANSLATED but was: REVIEWED at app//io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest.verifyStates$lambda$4(KeyControllerComplexEditTest.kt:184) at app//io.tolgee.util.TransactionUtilKt.executeInNewTransaction$lambda$0(transactionUtil.kt:24) at app//org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:140) at app//io.tolgee.util.TransactionUtilKt.executeInNewTransaction(transactionUtil.kt:23) at app//io.tolgee.util.TransactionUtilKt.executeInNewTransaction$default(transactionUtil.kt:11) at app//io.tolgee.AbstractSpringTest.executeInNewTransaction(AbstractSpringTest.kt:263) at app//io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest.verifyStates(KeyControllerComplexEditTest.kt:177) at app//io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest.doUpdateAndVerifyStates(KeyControllerComplexEditTest.kt:173) at app//io.tolgee.api.v2.controllers.v2KeyController.KeyControllerComplexEditTest.complex edit modifies state(KeyControllerComplexEditTest.kt:118) 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/
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/
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/
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 🏗️
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/
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)
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 ‍🔎 (security: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 ‍🔎 (data: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/
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/
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/
BT ‍🔎 (server-app:runWithoutEeTests)
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 ‍🔎 (server-app:runWebsocketTests)
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/
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/
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, 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, 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, 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, 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, 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, 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/
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/
BT ‍🔎 (server-app:runContextRecreatingTests)
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/
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, 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, 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, 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)
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 ‍🔎 (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:1b65cd42454226913010ee537fd1d612d1d46183f3afd481b26852f0b289800c
backend_test_reports_data_test
158 KB
sha256:666046812a0a70267dc821b601ac070ca90f6ab2937618c694b4b94dc941554b
backend_test_reports_ktlint_test
8.01 KB
sha256:df44cc54bc3efe752521781e54f2245e47248ea90ad22c6f5b5dbc47df32f17d
backend_test_reports_security_test
27.2 KB
sha256:2afc55b2818fe4bca4b5b10f604dae9c2ff189b31b0be07d6b297dd875a26e4d
backend_test_reports_server-app_runContextRecreatingTests
284 KB
sha256:e5ee9fbe88deaf3ca852f94ceccbbc87a2170064c094d72d65e04c0163568999
backend_test_reports_server-app_runStandardTests
863 KB
sha256:daa62bd2f55640651075103c55544c104c802bca8faedf8ac2f8d009ed1e52b5
backend_test_reports_server-app_runWebsocketTests
113 KB
sha256:86dbc60ad6c856ca120e9ba9fb29b45e1067457b4707838fb6ac6c9e5fe82c29
backend_test_reports_server-app_runWithoutEeTests
73.8 KB
sha256:7d3008ec6ad096303a3c6cdd01b6f6ba4ecef09fb2943742f37836ad04038538
e2e_13
122 KB
sha256:579f9d1e1e19249dfe6f6be2f338ce85032f58efbc825e561ed3a0f38860d202
e2e_deps
181 MB
sha256:1d54004925decf021ed30949c9b7220fd37f89c6ed0bb108408c73df75b047e8
e2e_server_log_13
600 KB
sha256:d0de8b1df9a515d424e5708306c4bfbf381d0e4e279a27b831a80ce925154800
e2e_server_log_8
886 KB
sha256:71481e715ad1b4d7fb878d1ebe9b91233601ab6c390c36aabba73e38409bf2c4
webapp
2.76 MB
sha256:0c6b1268671ecf59ae6876ee6f34016b4db395dab8b411bf4e83946b93a0a6f3