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.0: cli: unskip TestUnavailableZip #101941

Merged
merged 2 commits into from
Apr 20, 2023

Conversation

blathers-crl[bot]
Copy link

@blathers-crl blathers-crl bot commented Apr 20, 2023

Backport 2/2 commits from #100678 on behalf of @aadityasondhi.

/cc @cockroachdb/release


cli: make debug zip resilient to single failures

This fixes a regression in debug zip where a timeout failure in calls to
the status server would fail the entire collection of debug zip. We
instead want to continue trying all endpoints instead.


cli: unskip TestUnavailableZip

Fixes: #53306

Release note: None


Release justification: GA blocker / bugfix

This fixes a regression in debug zip where a timeout failure in calls to
the status server would fail the entire collection of debug zip. We
instead want to continue trying all endpoints instead.

Release note: None
Fixes: #53306

Release note: None
@blathers-crl blathers-crl bot requested a review from a team April 20, 2023 18:57
@blathers-crl blathers-crl bot requested a review from a team as a code owner April 20, 2023 18:57
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-23.1.0-100678 branch 2 times, most recently from 9679b6c to 4262179 Compare April 20, 2023 18:57
@blathers-crl blathers-crl bot added blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. labels Apr 20, 2023
@blathers-crl
Copy link
Author

blathers-crl bot commented Apr 20, 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

@aadityasondhi aadityasondhi merged commit 06fea49 into release-23.1.0 Apr 20, 2023
@aadityasondhi aadityasondhi deleted the blathers/backport-release-23.1.0-100678 branch April 20, 2023 20:38
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.

4 participants