Skip to content

KAFKA-18652: Add num.warmup.replicas config (#21801) #28617

KAFKA-18652: Add num.warmup.replicas config (#21801)

KAFKA-18652: Add num.warmup.replicas config (#21801) #28617

Triggered via push April 28, 2026 18:23
Status Success
Total duration 5h 33m 9s
Artifacts 21

ci.yml

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

Annotations

10 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 (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 (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 (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
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 / 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/
build / Update 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 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:1e5ada81e48e24999cce65244e8cb37d44665ad9db0b61464e59dd996cf38cb6
build-scan-17-noflaky-new
1.49 MB
sha256:2faeacb02b3e3b2fe9b86f014d803b6923521333bc193db57e7474bfdb2fde3b
build-scan-17-noflaky-nonew
6.81 MB
sha256:d550047a960d2cd507243c9afcbc23be4f29eda8170f1b9bcd2cd37a334df330
build-scan-25-flaky-nonew
1.46 MB
sha256:b5f1cc8c25cf4052942637d833f87315a6aa93748376824bbfe1b0c6cf486ffd
build-scan-25-noflaky-new
1.49 MB
sha256:725aa2a93ae08068ea725eb0d29dd87167ec25f7dd14ac10177da6a26ea62464
build-scan-25-noflaky-nonew
6.79 MB
sha256:c491d3db594427d3edd6459c79ed4bf7c1cfa6e41abb3d5b8f922de6f92f20a8
check-reports
4.66 MB
sha256:be359101b027c1ff8204570538a8aa5253e5d0595481f96c05f306da131cdf73
combined-test-catalog
226 KB
sha256:2f03132e1fe226d6a511b0b72b8d1d5a44e1245f1de6cac5710f82813de00d6d
junit-reports-17-flaky-nonew
932 KB
sha256:b46d4c3bda3a78e4b2a6e1f9c1652e2e28418a443e4b2789a51951032c6465fe
junit-reports-17-noflaky-new
540 KB
sha256:89f2e1d6d32112d86808fc9fe0bfe6aaad3876802fb92d653b87c9d821d5a684
junit-reports-17-noflaky-nonew
85.7 MB
sha256:d6f2fa8b417f43b31d1a1ebc89efce313c1aee4c80a119bdce913c0e40fe9142
junit-reports-25-flaky-nonew
933 KB
sha256:27045ede27fdc42fefc50f491e21e447ac5f012c2f20a715952d1bd7b34b8205
junit-reports-25-noflaky-new
543 KB
sha256:b41a317d0f277bd9a32eba0da236d5d3c53233aa1ffe59ef06feda17d8b4cff6
junit-reports-25-noflaky-nonew
85.9 MB
sha256:4492285b397012187a46d5a75698c675c9407ba541be5fcf425fe6de0fa78b2c
junit-xml-17-flaky-nonew
601 KB
sha256:553b87e7dae83ea83df63aaf73944ea0ee66d056b324359bbdcbb15bfb2838a0
junit-xml-17-noflaky-new
112 KB
sha256:fa6c67d4c4ed6b03841ea887f333d52d3ef3e7becf23e55123c97152ac2fc30f
junit-xml-17-noflaky-nonew
59.5 MB
sha256:9fe0736644e9eeed6fc57c1a20200052140abae82b6ab40a8d1ea0e09f0a7214
junit-xml-25-flaky-nonew
602 KB
sha256:633c64aae0aa70f6c16fd8afe416705f734568885e6fd11de6bd8f6030ad7903
junit-xml-25-noflaky-new
113 KB
sha256:fcfdbcf907b432bb61fd071ba032d28a19c24cc3f43fad6b171d15148462e2b7
junit-xml-25-noflaky-nonew
59.5 MB
sha256:9efa30a54bd5e9622e9264fcca17eb02b943089ac3ae436e836bf506b4da8668
test-catalog
203 KB
sha256:b583062d30e7633edaae0585db4a34d63d179005818c9339e167334342132c40