Turn off mixed version tests against Khepri #11663
Conversation
the-mikedavis
force-pushed
the
md/ci/turn-off-mixed-version-khepri-tests
branch
from
ad50399
to
8aedc68
Compare
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.
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.
…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.
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.
the-mikedavis
force-pushed
the
md/ci/turn-off-mixed-version-khepri-tests
branch
from
8aedc68
to
95279a3
Compare
|
Part of this PR is updating suites to respect the Before the last force-push this branch included some of the changes to bump Khepri to 0.14.0 from #11247 which has mixed-test failures in mnesia jobs. There are more places we could use |
Turn off mixed version tests against Khepri (backport #11663)
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.