separate-process deployments were added to the mixedversion framework in #130194. At that point, only a subset of tests were opted-in to this new deployment mode. Most tests that are known to fail (for non-obvious reasons) in that deployment mode had it disabled.
We should look at the failures more closely and enable separate-process on the following tests:
[ ] follower-reads/mixed-version/*
[ ] rebalance-load/*/mixed-version
[ ] backup-restore/mixed-version
[ ] import/mixed-versions
[ ] decommission/mixed-versions
[ ] validate-system-schema-after-version-upgrade (only in local mode)
[ ] acceptance/version-upgrade (only in local mode)
separate-process
deployments were added to the mixedversion framework in #130194. At that point, only a subset of tests were opted-in to this new deployment mode. Most tests that are known to fail (for non-obvious reasons) in that deployment mode had it disabled.We should look at the failures more closely and enable separate-process on the following tests:
follower-reads/mixed-version/*
rebalance-load/*/mixed-version
backup-restore/mixed-version
import/mixed-versions
decommission/mixed-versions
validate-system-schema-after-version-upgrade
(only in local mode)acceptance/version-upgrade
(only in local mode)Jira issue: CRDB-42310