Skip to content

redpandatest: retry broker container startup on readiness timeout#4313

Merged
josephwoodward merged 1 commit intomainfrom
mmt/redpandatest-fixes-v2
Apr 30, 2026
Merged

redpandatest: retry broker container startup on readiness timeout#4313
josephwoodward merged 1 commit intomainfrom
mmt/redpandatest-fixes-v2

Conversation

@mmatczuk
Copy link
Copy Markdown
Contributor

Commits

  • retry broker container startup on readiness timeout

Jira

  • CON-450

The Redpanda testcontainers module applies a hardcoded 60s wait per
readiness strategy. Under Docker pressure the broker occasionally fails
to start within that window, surfacing as a "wait for readiness: ...
context deadline exceeded" error. Retry the Run call up to three times
before failing so transient Docker slowness does not flake tests built
on StartSingleBrokerWithConfig.

Fixes CON-450
@claude
Copy link
Copy Markdown

claude Bot commented Apr 20, 2026

Commits
LGTM

Review
Small, focused change adding a retry loop around tcredpanda.Run in the test helper to handle transient Docker pressure causing the 60s readiness timeout to fire.

LGTM

This was referenced Apr 20, 2026
@josephwoodward josephwoodward merged commit 24d35a5 into main Apr 30, 2026
6 checks passed
@josephwoodward josephwoodward deleted the mmt/redpandatest-fixes-v2 branch April 30, 2026 15:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants