Repository navigation
ci: run the release test step against a real redis:7 - #11
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
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 release workflow ran pytest with BQ_CONFORMANCE_RESULTS set but without a Redis service, the redis extra or BQ_REQUIRE_REDIS. Conformance 1.6.0 redis_layout cases need a real Redis, so they were reported as failures and tests/test_conformance.py::ResultsJsonTest failed ('conformance failures differ from conformance-known-gaps.json'), blocking the v1.22.0 publish. This aligns release.yml with the ci.yml conformance job: redis:7 service, redis extra, BQ_REQUIRE_REDIS=1, BABELQUEUE_TEST_REDIS. No product code or version change.