Files
Groene AIandClaude Opus 4.8 71394c38b9 Cover all Kafka teardown delete_topics paths with retry
The previous commit added a retry-on-exception loop only to the shared
single-topic helper kafka_delete_topic. The same unprotected delete_topics
RPC existed in two other teardown paths, so a transient broker/controller
error during cleanup could still fail an otherwise-passing test:

- test_produce_http_interface.py defined its own duplicate kafka_create_topic
  and kafka_delete_topic; the local kafka_delete_topic called delete_topics
  once with no retry. Dropped both duplicates and reused the shared helpers
  in helpers.kafka.common (single source of truth).

- The shared bulk helper clean_test_database_and_topics issued an unprotected
  bulk delete_topics(topics). Wrapped it in the same retry loop.

- Eleven test_storage_kafka tests inlined a byte-identical copy of that bulk
  teardown. Converged them onto the now-retry-protected
  clean_test_database_and_topics so every Kafka delete_topics RPC in the
  integration suite goes through a retry path. Removed imports left unused
  after the convergence.

Net 30 insertions / 337 deletions. After the change the only delete_topics
call sites in tests/integration are the two retry-protected helpers.

Co-Authored-By: Claude Opus 4.8 <[email protected]>
2026-06-26 19:33:36 +00:00
..