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-22.2: kvserver: deflake TestLeasePreferencesDuringOutage #104125

Merged
merged 1 commit into from
May 31, 2023

Conversation

blathers-crl[bot]
Copy link

@blathers-crl blathers-crl bot commented May 31, 2023

Backport 1/1 commits from #103636 on behalf of @aliher1911.

/cc @cockroachdb/release


Test didn't accomodate for lease type changes on the same leaseholder in its assertions.

Release note: None

Fixes #103398


Release justification: Test only fix

Test didn't accomodate for lease type changes on the same
leaseholder in its assertions.

Release note: None
@blathers-crl blathers-crl bot requested a review from a team as a code owner May 31, 2023 00:01
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-22.2-103636 branch from a352084 to 533ae98 Compare May 31, 2023 00:01
@blathers-crl blathers-crl bot added blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. labels May 31, 2023
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-22.2-103636 branch from 7a85c83 to c6e0dea Compare May 31, 2023 00:01
@blathers-crl
Copy link
Author

blathers-crl bot commented May 31, 2023

Thanks for opening a backport.

Please check the backport criteria before merging:

  • Patches should only be created for serious issues or test-only changes.
  • 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

@aliher1911 aliher1911 merged commit abb096b into release-22.2 May 31, 2023
@aliher1911 aliher1911 deleted the blathers/backport-release-22.2-103636 branch May 31, 2023 09:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants