Skip to content

Conversation

fqazi
Copy link
Collaborator

@fqazi fqazi commented Oct 3, 2025

Backport 2/2 commits from #152112 on behalf of @fqazi.


Previously, the successful backup tests would for each stage of a schema
change would run the full schema change, taking a backup at the target
stage. This patch modifies the TestBackupSuccess variants of the schema
changer test to start the server once, take all the backups and then
restore the stages we should be testing.

Testing show around a ~30% improvement with this change in execution
time.

Fixes: #152076

Release note: None


Release justification: test only change

fqazi added 2 commits August 19, 2025 19:01
Previously, we only supported running a closure against a TestServer in
the schema changer testing framework. This was problematic for tests
that could save time by sharing servers (for example BACKUP / RESTORE).
To address this, this patch introduces a Start method for starting up a
server.

Release note: None
Previously, the successful backup tests would for each stage of a schema
change would run the full schema change, taking a backup at the target
stage. This patch modifies the TestBackupSuccess variants of the schema
changer test to start the server once, take all the backups and then
restore the stages we should be testing.

Testing show around a ~30% improvement with this change in execution
time.

Fixes: cockroachdb#152076

Release note: None
@fqazi fqazi requested a review from a team as a code owner October 3, 2025 11:50
@fqazi fqazi force-pushed the blathers/backport-release-25.3-152112 branch from 678f0c6 to f95be21 Compare October 3, 2025 11:50
@blathers-crl blathers-crl bot added blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. labels Oct 3, 2025
@blathers-crl blathers-crl bot requested a review from rafiss October 3, 2025 11:50
Copy link

blathers-crl bot commented Oct 3, 2025

Thanks for opening a backport.

Before merging, please confirm that the change does not break backwards compatibility and otherwise complies with the backport policy. Include a brief release justification in the PR description explaining why the backport is appropriate. All backports must be reviewed by the TL for the owning area. While the stricter LTS policy does not yet apply, please exercise judgment and consider gating non-critical changes behind a disabled-by-default feature flag when appropriate.

@blathers-crl blathers-crl bot added backport Label PR's that are backports to older release branches T-sql-foundations SQL Foundations Team (formerly SQL Schema + SQL Sessions) labels Oct 3, 2025
Copy link

blathers-crl bot commented Oct 3, 2025

It looks like your PR touches production code but doesn't add or edit any test code. Did you consider adding tests to your PR?

🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.

@cockroach-teamcity
Copy link
Member

This change is Reviewable

@rafiss rafiss added the backport-test-only Used to denote the backport has only non-production changes label Oct 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport Label PR's that are backports to older release branches backport-test-only Used to denote the backport has only non-production changes blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. T-sql-foundations SQL Foundations Team (formerly SQL Schema + SQL Sessions)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants