Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

release-21.2: backupccl: disable multi-region TestRestoreOldVersions under race #71389

Merged
merged 1 commit into from
Nov 15, 2021

Conversation

blathers-crl[bot]
Copy link

@blathers-crl blathers-crl bot commented Oct 11, 2021

Backport 1/1 commits from #71382 on behalf of @otan.

/cc @cockroachdb/release


Release note: None


Release justification:

@blathers-crl blathers-crl bot requested review from a team and dt and removed request for a team October 11, 2021 05:15
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-21.2-71382 branch from 245bd61 to fbd543f Compare October 11, 2021 05:15
@blathers-crl
Copy link
Author

blathers-crl bot commented Oct 11, 2021

Thanks for opening a backport.

Please check the backport criteria before merging:

  • Patches should only be created for serious issues.
  • Patches should not break backwards-compatibility.
  • Patches should change as little code as possible.
  • Patches should not change on-disk formats or node communication protocols.
  • Patches should not add new functionality.
  • Patches must not add, edit, or otherwise modify cluster versions; or add version gates.
If some of the basic criteria cannot be satisfied, ensure that the exceptional criteria are satisfied within.
  • There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
  • The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
  • New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters.
  • The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.

Add a brief release justification to the body of your PR to justify this backport.

Some other things to consider:

  • What did we do to ensure that a user that doesn’t know & care about this backport, has no idea that it happened?
  • Will this work in a cluster of mixed patch versions? Did we test that?
  • If a user upgrades a patch version, uses this feature, and then downgrades, what happens?

@cockroach-teamcity
Copy link
Member

This change is Reviewable

@dt
Copy link
Member

dt commented Oct 11, 2021

nit: s/Resolve/Restore/

@otan otan changed the title release-21.2: backupccl: disable multi-region TestResolveOldVersions under race release-21.2: backupccl: disable multi-region TestRestoreeOldVersions under race Oct 13, 2021
@otan otan changed the title release-21.2: backupccl: disable multi-region TestRestoreeOldVersions under race release-21.2: backupccl: disable multi-region TestRestoreOldVersions under race Oct 13, 2021
@otan otan merged commit 53bb848 into release-21.2 Nov 15, 2021
@otan otan deleted the blathers/backport-release-21.2-71382 branch November 15, 2021 20:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants