Skip to content

KAFKA-20422: Add DSL integration tests for header stores with explici… #28373

KAFKA-20422: Add DSL integration tests for header stores with explici…

KAFKA-20422: Add DSL integration tests for header stores with explici… #28373

Triggered via push April 21, 2026 01:51
Status Failure
Total duration 2h 55m 11s
Artifacts 20

ci.yml

on: push
build  /  Configure Workflow
3s
build / Configure Workflow
build  /  Compile and Check (Merge Ref)
11m 27s
build / Compile and Check (Merge Ref)
build  /  Load Test Catalog
14s
build / Load Test Catalog
Matrix: build / test
build  /  Collate Test Catalog
build / Collate Test Catalog
build  /  CI checks completed
2s
build / CI checks completed
build  /  Update Test Catalog
build / Update Test Catalog
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 8 warnings
build / JUnit tests Java 25 (new)
Process completed with exit code 1.
build / CI checks completed
Process completed with exit code 1.
build / Load Test Catalog
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
build / Compile and Check (Merge Ref)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
build / JUnit tests Java 25 (flaky)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, 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/
build / JUnit tests Java 17 (flaky)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, 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/
build / JUnit tests Java 25 (new)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, 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/
build / JUnit tests Java 17 (new)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, 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/
build / JUnit tests Java 17
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, 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/
build / JUnit tests Java 25
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5, 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
build-scan-17-flaky-nonew
1.46 MB
sha256:06019e0ad4506b27da0e09c91cacb1c2f0e99a5157d7864a0fd629660f6e973a
build-scan-17-noflaky-new
1.53 MB
sha256:d3b9506d81441ff27da3adde48986017dec73c621550951e76e3086243c6d6af
build-scan-17-noflaky-nonew
6.8 MB
sha256:ed122c7dc843cf8cb738aa2b87146f916909a6030008ac2afefa5a18dbac8a6a
build-scan-25-flaky-nonew
1.73 MB
sha256:4eeeb6e225666a9ecceac9153439c8899acdaa2cedb8d7d93a3931de7b2d9623
build-scan-25-noflaky-new
1.55 MB
sha256:1c72122bf2a6394e770df13588e8368a8610864f3159fae4c8c33460e00b8399
build-scan-25-noflaky-nonew
6.86 MB
sha256:71c3fd24721f19e88647c82ee899f5962d7b4876fa2002baeccccb01f73de5b9
check-reports
4.66 MB
sha256:f2479cc7358105b57ef283d3363ea05870137678da41b079ec0dc956c360ac0a
combined-test-catalog
226 KB
sha256:f4f203a671b247ae49f3d3006074338dc34864df1c772f2071782b84e0d271f4
junit-reports-17-flaky-nonew
943 KB
sha256:60f95c777b0928f21fef2cd3f638bec87a9b2a4ed2ec65c5cd906418f59a80b2
junit-reports-17-noflaky-new
862 KB
sha256:541c6e6cc596da11d9f348d3684e4f99a9baeda3e9bec14d8258dffb9b6eec9e
junit-reports-17-noflaky-nonew
84.6 MB
sha256:aa1a49e73dd2722f4ff51057926bec65e3b7bd1c86a49936b5460c674e7b5669
junit-reports-25-flaky-nonew
1.07 MB
sha256:47d8088862a93dd7ab549d49a72ca09fcc2b3b3efb34c318e66a50e784287570
junit-reports-25-noflaky-new
869 KB
sha256:fd0caab44c830e4c3e160528c42ff2f403d7e331d54fe02700dcf5e0afa5c541
junit-reports-25-noflaky-nonew
86.3 MB
sha256:4e6bc94e3bfce1349c8af25e6ceccc0b60b89da8b99d2a2d308cb29b329d8015
junit-xml-17-flaky-nonew
611 KB
sha256:fad41b53689fb2a0b2ef52298ded340a7175ccddd0dc9163439067bef66bb5ed
junit-xml-17-noflaky-new
289 KB
sha256:85b13c1839918a6a552a3b20af8c73fbd7f9d6d6b497791d289f214ff556c176
junit-xml-17-noflaky-nonew
58.3 MB
sha256:e17cf367780af6cb183180903f0b3a73245b3f9ecaa7e97ecfcc83a3c766a636
junit-xml-25-flaky-nonew
759 KB
sha256:9ef104d38c06b73d8dadae4ff1e431f79916a3ddb772fdb5c8bfa05bfb1dc425
junit-xml-25-noflaky-new
290 KB
sha256:e96a42dc34b5d9443b5d1053dec4aa09ccabf73e386147576948eabf533bf274
junit-xml-25-noflaky-nonew
59.9 MB
sha256:6821615c11816681b136adf600ff9c62aa66f6929fce4ad3fa424f3ee447d029