Skip to content

KAFKA-20699: TopologyTestDriver.getStateStore must not reset the record context #30359

KAFKA-20699: TopologyTestDriver.getStateStore must not reset the record context

KAFKA-20699: TopologyTestDriver.getStateStore must not reset the record context #30359

Re-run triggered June 16, 2026 14:54
Status Success
Total duration 1h 2m 40s
Artifacts 19

ci.yml

on: pull_request
build  /  Configure Workflow
3s
build / Configure Workflow
build  /  Compile and Check (Merge Ref)
5m 20s
build / Compile and Check (Merge Ref)
build  /  Load Test Catalog
19s
build / Load Test Catalog
Matrix: build / test
build  /  Collate Test Catalog
17s
build / Collate Test Catalog
build  /  CI checks completed
5s
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 16th, 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 16th, 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 16th, 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 16th, 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 16th, 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 16th, 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 16th, 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 16th, 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 16th, 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.34 MB
sha256:c2a4713d5c6f8a240e959c6de745c10adc335b41047a8683812ef55f08e18fef
build-scan-17-noflaky-new
1.4 MB
sha256:bf2595a1b1a15f3f98993f35cfdb58ab20095c1dd30ff67877ff28074a3c5908
build-scan-17-noflaky-nonew
2.14 MB
sha256:5bbf36ac8457cbe320771334408d6c0ab35a99056d477a31efb25133e5ab7aeb
build-scan-25-flaky-nonew
1.35 MB
sha256:0d1141b0af8b0cc5ee7f7ae0ce0b9633ba68d56cac374dfa82a03cea666b4d60
build-scan-25-noflaky-new
1.4 MB
sha256:face7b17a6c7eea30b255223b3eb0614d25af0860188ba9ed926f2ed682c0649
build-scan-25-noflaky-nonew
2.14 MB
sha256:5c42ed9f51879f511c0129c34eb4fac882535a4845c2bcbca77b539b883246f4
check-reports
4.75 MB
sha256:1f16c1b831a6e07f41927053d5ff1aedbe2d776a89acde7ce7f5320cdb706d4b
combined-test-catalog
233 KB
sha256:21014b33a60241803ae75244f650004c3ebeb24b44213ad3e2e8e596ce4a0cc7
junit-reports-17-flaky-nonew
873 KB
sha256:b928ae8026d9c4ddfc141952eaac39a0ad77ba936f31fb908bca780dcce53cd1
junit-reports-17-noflaky-new
472 KB
sha256:3fd83325fccfa04548c576bed2b27be95a723e28bd040c48094f118bc871055b
junit-reports-17-noflaky-nonew
85.8 MB
sha256:dad00c843f682df8fedb7de2b1f6d88895a2d192703c7a7e50a3c9f693af624a
junit-reports-25-flaky-nonew
890 KB
sha256:bd3971cefcbf0a6015c53c74a6ff1a0bd4a2ac22a39b1c66df6df29dec767c58
junit-reports-25-noflaky-new
473 KB
sha256:b9a015572cfcea74d82d6254c723aa8c0d20623f19fa7d7209edfd890d07f7f6
junit-reports-25-noflaky-nonew
85.2 MB
sha256:4bde020bdf89655fadad301971af4bfef7723b44af0fa0f59cd91c0a12bed521
junit-xml-17-noflaky-new
94.6 KB
sha256:743fa24364b31b7185b7c0d946c1787ce7cd114772a76260bd8328a2b3027448
junit-xml-17-noflaky-nonew
12.1 MB
sha256:6297cd6d01e8693e9f63ae6fd125a1fcf09473947b2bc793a41aa6d8ad5c5c5a
junit-xml-25-noflaky-new
93.8 KB
sha256:f89f7e47485d9310cf49ff59e2890364487041e50da8002e0938aae0bd98d01b
junit-xml-25-noflaky-nonew
11.4 MB
sha256:2659bc43c1139b668c75996095a61d510d1d6c788277c90d018f65899018ad43
test-catalog
58.1 KB
sha256:efcc225165771cb04378cc2de8eff5473065ca677d05c58266c7aade495c1fb8