Pin RabbitMQ broker image to 3.x in Celery tests#681
Merged
Conversation
RabbitMQ 4.x removed transient_nonexcl_queues, which Celery/kombu uses for the mingle boot-step. Pin to rabbitmq:3 via the default_rabbitmq_broker_image fixture override provided by pytest-celery for exactly this purpose.
There was a problem hiding this comment.
Pull request overview
Pins the RabbitMQ Docker image used by the test_celery_remote integration test setup to RabbitMQ 3.x to prevent CI failures caused by RabbitMQ 4.x removing/locking down the transient_nonexcl_queues behavior required by Celery/kombu during worker startup.
Changes:
- Add a local
default_rabbitmq_broker_imagefixture override forpytest-celery. - Return
"rabbitmq:3"instead of relying onrabbitmq:latest.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #681 +/- ##
=======================================
Coverage 83.44% 83.44%
=======================================
Files 14 14
Lines 610 610
=======================================
Hits 509 509
Misses 101 101
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Contributor
Author
|
Squash commit message: Title Body |
This was referenced May 11, 2026
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
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.
Summary
Pin the RabbitMQ Docker image used by the
test_celery_remotetests torabbitmq:3instead ofrabbitmq:latest.RabbitMQ 4.x removed support for the
transient_nonexcl_queuesfeature, which Celery/kombu requires during worker startup, causing all Linux CI jobs to fail.Motivation
Fixes #680
The
pytest-celerylibrary defaults torabbitmq:latestfor its broker container.A recent promotion of RabbitMQ 4.x to that tag broke the
test_celery_remotetest on every Linux runner, blocking every incoming PR (e.g. #677).Changes
tests/strategies/transformation/conftest.py(new file)Override the
default_rabbitmq_broker_imagefixture — the extension point thatpytest-celeryexplicitly exposes for this purpose — to return"rabbitmq:3".No other test behaviour changes.
Test Plan
pre-commit run -apasses with no modificationstest_celery_remotepasses on Linux runners (verified by CI on this PR)Generated using AI.