Repository navigation
install mosquitto from the ubuntu archive in conformance ci - #215
Merged
Merged
Conversation
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
1 participant
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 Mosquitto interop job kept failing on image pulls. Docker Hub refused
eclipse-mosquitto:2withtoomanyrequests: You have reached your unauthenticated pull rate limit, and after #214 moved the pull to ECR Public, the next run failed there withtoomanyrequests: Rate exceeded. Hosted runners share IP addresses, so any anonymous registry pull can run into a limit.The job now installs Mosquitto from the Ubuntu archive, stops the service the package starts, and runs it with the same config as before, logging to
mosquitto.log.This changes the version under test.
eclipse-mosquitto:2currently resolves to 2.1.2, and Ubuntu 24.04 ships 2.0.18. The fixture covers 2.x, and the job runs onlydeferred_qos2. Locally, against Ubuntu 24.04's package in a container, both tests in that group pass, as they do against the 2.1.2 image, and both fail with no broker running.