Skip to content

KAFKA-17251: Avoid WARN on cleanup when state directory only contains process metadata. #28352

KAFKA-17251: Avoid WARN on cleanup when state directory only contains process metadata.

KAFKA-17251: Avoid WARN on cleanup when state directory only contains process metadata. #28352

Re-run triggered April 20, 2026 13:28
Status Cancelled
Total duration 36m 6s
Artifacts 16

ci.yml

on: pull_request
build  /  Configure Workflow
4s
build / Configure Workflow
build  /  Compile and Check (Merge Ref)
5m 13s
build / Compile and Check (Merge Ref)
build  /  Load Test Catalog
15s
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
0s
build / Update Test Catalog
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 8 warnings
build / JUnit tests Java 25
Canceling since a higher priority waiting request for CI-20969 exists
build / JUnit tests Java 25
The operation was canceled.
build / JUnit tests Java 17
Canceling since a higher priority waiting request for CI-20969 exists
build / JUnit tests Java 17
The operation was canceled.
build / CI checks completed
Process completed with exit code 1.
CI
Canceling since a higher priority waiting request for CI-20969 exists
CI
Canceling since a higher priority waiting request for CI-20969 exists
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 (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 (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
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/

Artifacts

Produced during runtime
Name Size Digest
build-scan-17-flaky-nonew
1.4 MB
sha256:b92dc9238823bad78ee9b495e869b27ab91e85c218dfc73cb9a438a25c52df86
build-scan-17-noflaky-new
1.42 MB
sha256:0869a00a4208f5ffac6903b0b425845c59c4fccfe9ae30706301e3e71389f3b3
build-scan-17-noflaky-nonew
2.06 MB
sha256:558665e82ca14c97920706bdeb8d3b24391d97cd50fcd12b3ccca620c146d7ee
build-scan-25-flaky-nonew
1.4 MB
sha256:14b999b31d784e2811875204ac5b59352371b10b24c6aed9a4a0844b87390c07
build-scan-25-noflaky-new
1.42 MB
sha256:d23597ef44cc8d328d23e0473e9fa0cdc2873fd54f5c48e44a62cc190b5e3f65
build-scan-25-noflaky-nonew
2.07 MB
sha256:cc9a79459127df1e26390265983dde74e8314fe32824a675f39a10aec88e4f86
check-reports
4.65 MB
sha256:9a1a1fb272afa79294b4d7e081709f411f14ded275f25e1f752c7b9197148eb7
combined-test-catalog
226 KB
sha256:78a6fbd13bf6c4e0c983810a60158d6f671fc83c26cd5371a8fce11fc67d016d
junit-reports-17-flaky-nonew
924 KB
sha256:cd04b51f78897c6afc92ad804bdf470018f55fa093ae7f19ff8d0f73fa84333b
junit-reports-17-noflaky-new
451 KB
sha256:1afc8b6a39db1c7438395758c57acf5ce3b10fe88da2f55f32cf14b2bbce6be7
junit-reports-25-flaky-nonew
937 KB
sha256:a622a31c15bece22e83f33fd3bb4c6be9d3414b62b0f91264150a33c306d1aed
junit-reports-25-noflaky-new
452 KB
sha256:21b3e63999feff04824dbf1ee7684e2af8c0ca947c350362c16099612c740658
junit-xml-17-flaky-nonew
594 KB
sha256:f18e43e0f7ff5cd67ee832d54c1bbb25dc5446b82ec034fb93ee6ad91714858c
junit-xml-17-noflaky-new
92.9 KB
sha256:2ce191e71c3255533b32e408b3b8318c8afed8223ac42ad05eec609c89dedb39
junit-xml-25-flaky-nonew
605 KB
sha256:932d810e6e0988c4a2c1f043b9f190a62c5bed9a73023d9493632ebdb704e837
junit-xml-25-noflaky-new
92 KB
sha256:7d925b4817b354699392e062b93d042f880c90c29b70fdcc7e4d36aa9413c091