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-23.1: rpc: deflake TestHeartbeatDialback #105611

Merged
merged 1 commit into from
Jun 27, 2023

Conversation

tbg
Copy link
Member

@tbg tbg commented Jun 27, 2023

require.ErrorAs mutates. We don't want that here.

Closes #105134.

Epic: none
Release note: None
Release justification: test flake fix

`require.ErrorAs` mutates. We don't want that here.

Closes cockroachdb#105134.

Epic: none
Release note: None
@blathers-crl
Copy link

blathers-crl bot commented Jun 27, 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

@tbg tbg requested a review from pav-kv June 27, 2023 12:28
@tbg tbg marked this pull request as ready for review June 27, 2023 12:28
@tbg tbg requested a review from a team as a code owner June 27, 2023 12:28
@tbg tbg merged commit 4c7ff06 into cockroachdb:release-23.1 Jun 27, 2023
@tbg tbg deleted the TestVerifyDialback branch June 27, 2023 14:50
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