Skip to content

KAFKA-20417: Add KIP-1035 self-managed offset lifecycle integration tests #27915

KAFKA-20417: Add KIP-1035 self-managed offset lifecycle integration tests

KAFKA-20417: Add KIP-1035 self-managed offset lifecycle integration tests #27915

Triggered via pull request April 8, 2026 14:24
Status Success
Total duration 2h 8m 39s
Artifacts 19

ci.yml

on: pull_request
build  /  Configure Workflow
4s
build / Configure Workflow
build  /  Compile and Check (Merge Ref)
5m 26s
build / Compile and Check (Merge Ref)
build  /  Load Test Catalog
17s
build / Load Test Catalog
Matrix: build / test
build  /  Collate Test Catalog
23s
build / Collate Test Catalog
build  /  CI checks completed
3s
build / CI checks completed
build  /  Update Test Catalog
0s
build / Update Test Catalog
Fit to window
Zoom out
Zoom in

Annotations

9 warnings
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 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/
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 / Collate Test Catalog
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.36 MB
sha256:763db3af5cb5c6ebc7b7c45960fb40145df226598134e66ab9b66f39baf05f5f
build-scan-17-noflaky-new
1.41 MB
sha256:d2003cc9fec67f2abc80515a4f1ce5eb411937b712d6e23cdd6f30056b29dec9
build-scan-17-noflaky-nonew
5.18 MB
sha256:79ef3bd631bbc8bec71e0b73f9796edf47bc3c5948f5c49879453d499925b28f
build-scan-25-flaky-nonew
1.35 MB
sha256:6fedc2648c86fa3c06ccf0993befe411070b5b431c0d2f6d9b6004a4147ece7f
build-scan-25-noflaky-new
1.41 MB
sha256:0b973d6ad412f39f4e0ee2be5bf02f75a6c04d2dca5936c1c020c352b3a7734a
build-scan-25-noflaky-nonew
5.18 MB
sha256:3bf8a7dc2fbb61451d304d7899a863b0a48b581c70aca87c71ee78371fd8b352
check-reports
4.66 MB
sha256:0c39dad6159f7611c226449e5df09b6fd71c206025f0aae18434be9eecb1b214
combined-test-catalog
226 KB
sha256:6ae38c51691ede66d3362cd9b7add74c55330b0dc2eeae4b672613d36db3badd
junit-reports-17-flaky-nonew
909 KB
sha256:4238e7ed9d3c26a0a4f420fae390bc7b31c8a5ab8e503fdd0ec7bc1a2837bcb5
junit-reports-17-noflaky-new
560 KB
sha256:0d3aeff702fb4cd18e892f95c8bd2da7dbbffcb7352e27561a31820d2d6c99e0
junit-reports-17-noflaky-nonew
60.6 MB
sha256:b817fd7eb647c7f91301bd2cc83ae9a1b81a1ac37defc32f19b85f519420ae8f
junit-reports-25-flaky-nonew
884 KB
sha256:0ce83b6fabed13afdadc53ae9887e58b68634ebb444defa75c0bc6bb4c52fd2b
junit-reports-25-noflaky-new
561 KB
sha256:6bb4cf77a4661439636c0d17d6252ff6b3eadd6d19b69079c6bc59147085b7b9
junit-reports-25-noflaky-nonew
60.5 MB
sha256:1f24f8599366e2bd8f5b1bbd963e22adc5b7f1b34de9b17c9077b7b157876b9c
junit-xml-17-noflaky-new
273 KB
sha256:bf2b584a81fee2f1e17f39cf5b9d38c037e9abd70ade466bbbeb8a99e44a764d
junit-xml-17-noflaky-nonew
57.1 MB
sha256:2a78beabc320b7b2c4004be45e6904e92ea7a5c2b6982ce4d24da5350d94bdfc
junit-xml-25-noflaky-new
274 KB
sha256:5aa38c55ee8e0e095c93e2ed54cf95459f0aa1359d42e81e8c6a99c3ec7ea914
junit-xml-25-noflaky-nonew
56.9 MB
sha256:77b15e2093078e7dc60caed03eb904cfd0fdaf5a29904ce36521aff7343b3033
test-catalog
104 KB
sha256:669964ea5937103ee3b4b70309d5cc4872f7903f4d77e1abbd53ac891aa4ad3b