Pin RabbitMQ to last AiiDA-supported version in CI#271
Merged
Conversation
Later versions introduced default timeouts. The default timeout of 30 mins is actually fine for CI, but the AiiDA warnings about it are distracting noise if they show up in test logs. https://aiida.readthedocs.io/projects/aiida-core/en/latest/installation/troubleshooting.html#rabbitmq-incompatibility
alinelena
approved these changes
Apr 14, 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
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.
Later versions introduced default timeouts. The default timeout of 30 mins is actually fine for CI, but the AiiDA warnings about it are distracting noise if they show up in test logs.
https://aiida.readthedocs.io/projects/aiida-core/en/latest/installation/troubleshooting.html#rabbitmq-incompatibility
(As discussed in #270. Thanks @ElliottKasoar for hunting down the docs page!)
Alternatively we can disable the warning by some other means such as
verdi config set warnings.rabbitmq_version False. According to the AiiDA docs, that is necessary even if you increase the timeout.The simplest option for now seems to be a pin. It's only in the CI so doesn't impact users.