Skip to content

Turn off mixed version tests against Khepri (backport #11663) #11669

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Jul 10, 2024

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Jul 10, 2024

Khepri v0.14.0 creates problems for mixed-version tests: the new machine version causes commands and queries to fail on the nodes running the old version. We should separately fix these issues and eventually re-enable mixed version tests with Khepri as the feature stabilizes.


This is an automatic backport of pull request #11663 done by Mergify.

Khepri is experimental and not guaranteed to be upgradable. We should
re-enable mixed version testing as Khepri stabilizes but for now we
should turn it off.

This saves some CI time and avoids some failures that will be introduced
when we upgrade Khepri to v0.14.0.

(cherry picked from commit e08310a)
Khepri is not yet compatible with mixed-version testing and this suite
only tests clustering when Khepri is the metadata store in at least some
of the nodes.

(cherry picked from commit bda1f7c)
…esia

This suite is only meant to run with Khepri as the metadata store.
Instead of setting this explicitly we can look at the configured
metadata store and conditionally skip the entire suite. This prevents
these tests from running twice in CI.

(cherry picked from commit ecb7575)
@mergify mergify bot added the conflicts label Jul 10, 2024

This comment was marked as resolved.

Without buildbuddy for parallelization and with the change in the parent
commit to reduce the number of cases, the suite now runs fast enough
that sharding is counterproductive.

(cherry picked from commit 95279a3)

# Conflicts:
#	deps/rabbitmq_consistent_hash_exchange/BUILD.bazel
@the-mikedavis the-mikedavis force-pushed the mergify/bp/v3.13.x/pr-11663 branch from 208086c to 29d1a3f Compare July 10, 2024 20:09
@the-mikedavis the-mikedavis merged commit a0201b8 into v3.13.x Jul 10, 2024
188 checks passed
@the-mikedavis the-mikedavis deleted the mergify/bp/v3.13.x/pr-11663 branch July 10, 2024 20:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant