-
Notifications
You must be signed in to change notification settings - Fork 4.1k
roachtest: stop using versionUpgradeTest in acceptance/decommission-self #110530
Copy link
Copy link
Closed
Closed
Copy link
Labels
C-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)P-3Issues/test failures with no fix SLAIssues/test failures with no fix SLAT-testengTestEng TeamTestEng Teambranch-masterFailures and bugs on the master branch.Failures and bugs on the master branch.branch-release-23.2Used to mark GA and release blockers, technical advisories, and bugs for 23.2Used to mark GA and release blockers, technical advisories, and bugs for 23.2
Description
The acceptance/decommission-self test currently uses versionUpgradeTest and related functions even though the test is not an upgrade / mixed-version test. In order to make it less confusing and enable us to fully deprecate and remove versionUpgradeTest (in favour of the mixedversion framework), we should update that test to not use that function.
Jira issue: CRDB-31480
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
C-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)P-3Issues/test failures with no fix SLAIssues/test failures with no fix SLAT-testengTestEng TeamTestEng Teambranch-masterFailures and bugs on the master branch.Failures and bugs on the master branch.branch-release-23.2Used to mark GA and release blockers, technical advisories, and bugs for 23.2Used to mark GA and release blockers, technical advisories, and bugs for 23.2