ci(flink-smoke): bound the image build with a timeout and one retry - #220
Merged
Conversation
The PyFlink image build stalled silently on registry/PyPI pulls twice on doc-only PRs (#213, #218) — zero build output after the ca-certificates layer until the 30-min job timeout. The build is now its own bounded step (10 min, one retry) so a transient stall costs ~10 min and recovers, instead of eating the whole job; the wait-loop deadline was never the problem — it only starts after the build. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
DORA Metrics
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The flink-smoke PR lane hung twice on doc-only PRs (#213 cancelled 30m17s, #218 cancelled 30m15s): the PyFlink image build inside
docker compose up -d --buildstalled silently on registry/PyPI pulls (zero build output after the ca-certificates layer) and the job'stimeout-minutes: 30was the only thing that ended it. The step's own 10-min wait loop never engaged — it starts after the build.The build is now a separate bounded step:
timeout 600 docker compose build flink-job-runnerwith one retry, thenup -druns the locally built image. A transient network stall now costs ~10 min and self-recovers instead of eating the whole job and leaving a red non-required check.Contract test updated to pin the new shape (bounded build present,
up -dwithout--build); workflow-pinning + timeout suites green locally.🤖 Generated with Claude Code