Skip to content

release-25.2: backup: delete TestBackupRestoreWithConcurrentWrites#170644

Open
msbutler wants to merge 1 commit into
cockroachdb:release-25.2from
msbutler:blathers/backport-release-25.2-170607
Open

release-25.2: backup: delete TestBackupRestoreWithConcurrentWrites#170644
msbutler wants to merge 1 commit into
cockroachdb:release-25.2from
msbutler:blathers/backport-release-25.2-170607

Conversation

@msbutler
Copy link
Copy Markdown
Collaborator

Backport 1/1 commits from #170607 on behalf of @msbutler.


This test has been flaking a ton, and we already have coverage for this in the roachtest.

Fixes #170025

Release note: none


Release justification:

This test has been flaking a ton, and we already have coverage for this in the
roachtest.

Fixes cockroachdb#170025

Release note: none
@msbutler msbutler force-pushed the blathers/backport-release-25.2-170607 branch from 53ade71 to 307ffdb Compare May 20, 2026 14:13
@msbutler msbutler requested a review from a team as a code owner May 20, 2026 14:13
@msbutler msbutler requested review from dt and removed request for a team May 20, 2026 14:13
@blathers-crl blathers-crl Bot added blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. labels May 20, 2026
@blathers-crl blathers-crl Bot requested a review from kev-cao May 20, 2026 14:13
@trunk-io
Copy link
Copy Markdown
Contributor

trunk-io Bot commented May 20, 2026

Merging to release-25.2 in this repository is managed by Trunk.

  • To merge this pull request, check the box to the left or comment /trunk merge below.

After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here

@blathers-crl
Copy link
Copy Markdown

blathers-crl Bot commented May 20, 2026

Thanks for opening a backport.

Before merging, please confirm that it falls into one of the following categories (select one):

  • Non-production code changes OR fixes for serious issues. Non-production includes test-only changes, build system changes, etc. Serious issues are defined in the policy as correctness, stability, or security issues, data corruption/loss, significant performance regressions, breaking working and widely used functionality, or an inability to detect and debug production issues.
  • Other approved changes. These changes must be gated behind a disabled-by-default feature flag unless there is a strong justification not to. Reference the approved ENGREQ ticket in the PR body (e.g., "Fixes ENGREQ-123").

Add a brief release justification to the PR description explaining your selection.

Also, confirm that the change does not break backward compatibility and complies with all aspects of the backport policy.

All backports must be reviewed by the TL and EM for the owning area.

@blathers-crl blathers-crl Bot added backport Label PR's that are backports to older release branches T-disaster-recovery labels May 20, 2026
@cockroach-teamcity
Copy link
Copy Markdown
Member

This change is Reviewable

@blathers-crl blathers-crl Bot added the backport-test-only Used to denote the backport has only non-production changes label May 20, 2026
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-disaster-recovery

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants