Skip to content

Docs/edc extensions readmes (#2711) #5778

Docs/edc extensions readmes (#2711)

Docs/edc extensions readmes (#2711) #5778

Triggered via push April 16, 2026 10:59
Status Failure
Total duration 12m 14s
Artifacts 15
deployment-test  /  test-prepare
4s
deployment-test / test-prepare
upgradeability-test  /  test-prepare
3s
upgradeability-test / test-prepare
verify  /  prepare-end-to-end-tests
3s
verify / prepare-end-to-end-tests
Matrix: deployment-test / test-hashicorp-postgres
deployment-test  /  test-in-memory
3m 20s
deployment-test / test-in-memory
upgradeability-test  /  test-upgradeability
50s
upgradeability-test / test-upgradeability
Matrix: verify / end-to-end-tests
verify  /  generate-allure-report
25s
verify / generate-allure-report
summary
0s
summary
Fit to window
Zoom out
Zoom in

Annotations

1 error and 6 warnings
upgradeability-test / test-upgradeability
Process completed with exit code 1.
upgradeability-test / test-upgradeability
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: azure/setup-helm@v4, azure/setup-kubectl@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/
deployment-test / test-in-memory
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: azure/setup-helm@v4, azure/setup-kubectl@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/
deployment-test / test-hashicorp-postgres (v1.35.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: azure/setup-helm@v4, azure/setup-kubectl@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/
deployment-test / test-hashicorp-postgres (v1.33.7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: azure/setup-helm@v4, azure/setup-kubectl@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/
deployment-test / test-hashicorp-postgres (v1.34.3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: azure/setup-helm@v4, azure/setup-kubectl@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/
verify / generate-allure-report
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: peaceiris/actions-gh-pages@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
JaCoCo coverage-report
74.1 KB
sha256:301e593323308f84a2b261f048fe2be9a83111d890bfa8aee23d554e6e2c452c
allure-results-edc-tests-e2e-bpn-event-tests
3.44 KB
sha256:c911079ce6e95e2677eb385dafcd0126048f04343f0222151d983930e6bdde70
allure-results-edc-tests-e2e-catalog-tests
15.1 KB
sha256:99e141e1328222f9c052078877690c605254d77b715ac4a3423eb7f5596d700f
allure-results-edc-tests-e2e-cloud-transfer-tests
17 KB
sha256:d9cac9aa32964caf29f18adbe0f80e45138a5ecffe09f0b9f08adebb3bc2a3db
allure-results-edc-tests-e2e-dcp-tck-tests
24.3 KB
sha256:d502656ddac6113b1d88d7e3400b3cd0ba3cc403cb6e9d10e77e7fa7bc69dc26
allure-results-edc-tests-e2e-dcp-tests
25.9 KB
sha256:8263ed926571adab682a353649520dc2b8bbe63c398d98f008abb032d8912015
allure-results-edc-tests-e2e-discovery-tests
13.3 KB
sha256:bfe166759edc8e4d25df74257733193c10ae96f0e745b7a74e05e93739aa204d
allure-results-edc-tests-e2e-dsp-compatibility-tests
1.35 KB
sha256:bf09c408278a5f4d750fbc1b35e7a72824e8c0b2bd64c853ebd318a6037bdb29
allure-results-edc-tests-e2e-edc-dataplane-tokenrefresh-tests
11.3 KB
sha256:3b9ad02be733c9c1e3ce3b075c55011cfcf7b70e5456dacc65d753f2e5f71298
allure-results-edc-tests-e2e-edr-api-tests
10.2 KB
sha256:b66d2dd8870a050c745bfd70999fcdfae30ca61b43843b211911a73d8a2e9b71
allure-results-edc-tests-e2e-end2end-transfer-cloud
5.74 KB
sha256:244567014608bb66c5a934e10da7bb4c698b5bf2600b7f76c4c0e9947399be7c
allure-results-edc-tests-e2e-management-tests
4.88 KB
sha256:43bef439e005e75b3ce7299da708e710b3060530c039de37916703e42a82ee33
allure-results-edc-tests-e2e-policy-tests
77.5 KB
sha256:6f11d525d4087bd5c6b2c2f17aadce5e21575f23c52dc96cf25b311ad94e197a
allure-results-edc-tests-e2e-transfer-tests
40.5 KB
sha256:00db1fc3cdd0a59ff9719654b7e3cbf0444030f59098097fa57404d3acbfbfaa
code-coverage-report-markdown
6.07 KB
sha256:5fa49c2392a4dc9315012dc78e1d51cbf3a806b18ab04928e7f86fdc959369f1