Skip to content

roachtest/mixedversion: workload binary sync for schemachange/mixed-versions #154274

@williamchoe3

Description

@williamchoe3

See this PR desc for update #155397


Follow up to #147374
See this thread: #153269 (comment)

schemachange/mixed-versions uses a dedicated workload binary. This was previously not versioned.

Currently there's a limitation on this test

		// Disable version skipping and limit the test to only one upgrade as the workload is only
		// compatible with the branch it was built from and the major version before that.
		mixedversion.NumUpgrades(1),
		mixedversion.DisableSkipVersionUpgrades,

If workload binary is versioned, we should be able to remove this limitation.

Outcome of this is to verify the initial failure mode, then use a dedicated versioned workload binary and see if doing that remove's the current upgrade limitation for this test.

Test Failure (with versioned binary): https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/20520974?hideProblemsFromDependencies=false&hideTestsFromDependencies=false&expandBuildTestsSection=true&expandBuildChangesSection=true&expandBuildDeploymentsSection=false

Update: I think the initial failure I saw during my initial refactor was the same issue i'm seeing now where we can't find the specific binary on GCS.

Jira issue: CRDB-54845

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-testeng-foundationsA-testingTesting tools and infrastructureC-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)T-testengTestEng Team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions