Fix integration test timeouts in CI #34
Draft
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.
Integration tests were timing out in CI due to unbounded Docker image pulls during test execution. The
eclipse-mosquitto:latestimage pull could hang indefinitely without timeout handling.Changes
CI workflow
eclipse-mosquitto:latestwith 300s timeout before test executionTest fixtures
pull_docker_image_with_timeout()helper with configurable timeout (default: 300s)Makefile
Implementation
The fixture now checks for image availability and pulls with timeout only if needed, preventing the implicit unbounded pull during
containers.run().Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.