Skip to content

[release-21.0] Avoid terminating atomic copy workflows on error if they are out of copy phase (#18475)#18486

Merged
dbussink merged 1 commit intorelease-21.0from
backport-18475-to-release-21.0
Jul 25, 2025
Merged

[release-21.0] Avoid terminating atomic copy workflows on error if they are out of copy phase (#18475)#18486
dbussink merged 1 commit intorelease-21.0from
backport-18475-to-release-21.0

Conversation

@vitess-bot
Copy link
Copy Markdown
Contributor

@vitess-bot vitess-bot bot commented Jul 24, 2025

Description

This is a backport of #18475

…opy phase (#18475)

Signed-off-by: Noble Mittal <noblemittal@outlook.com>
@vitess-bot vitess-bot bot requested a review from rohit-nayak-ps as a code owner July 24, 2025 19:18
@vitess-bot vitess-bot bot added the Type: Bug label Jul 24, 2025
@vitess-bot vitess-bot bot requested review from deepthi and mattlord as code owners July 24, 2025 19:18
@vitess-bot vitess-bot bot requested review from beingnoble03 and notfelineit July 24, 2025 19:18
@vitess-bot
Copy link
Copy Markdown
Contributor Author

vitess-bot bot commented Jul 24, 2025

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

  • Ensure that the Pull Request has a descriptive title.
  • Ensure there is a link to an issue (except for internal cleanup and flaky test fixes), new features should have an RFC that documents use cases and test cases.

Tests

  • Bug fixes should have at least one unit or end-to-end test, enhancement and new features should have a sufficient number of tests.

Documentation

  • Apply the release notes (needs details) label if users need to know about this change.
  • New features should be documented.
  • There should be some code comments as to why things are implemented the way they are.
  • There should be a comment at the top of each new or modified test to explain what the test does.

New flags

  • Is this flag really necessary?
  • Flag names must be clear and intuitive, use dashes (-), and have a clear help text.

If a workflow is added or modified:

  • Each item in Jobs should be named in order to mark it as required.
  • If the workflow needs to be marked as required, the maintainer team must be notified.

Backward compatibility

  • Protobuf changes should be wire-compatible.
  • Changes to _vt tables and RPCs need to be backward compatible.
  • RPC changes should be compatible with vitess-operator
  • If a flag is removed, then it should also be removed from vitess-operator and arewefastyet, if used there.
  • vtctl command output order should be stable and awk-able.

@github-actions github-actions bot added this to the v21.0.6 milestone Jul 24, 2025
@codecov
Copy link
Copy Markdown

codecov bot commented Jul 24, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 67.53%. Comparing base (5244350) to head (3a23fea).

Additional details and impacted files
@@               Coverage Diff                @@
##           release-21.0   #18486      +/-   ##
================================================
+ Coverage         67.51%   67.53%   +0.01%     
================================================
  Files              1572     1572              
  Lines            252347   252347              
================================================
+ Hits             170383   170432      +49     
+ Misses            81964    81915      -49     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@dbussink dbussink merged commit 51ac5b4 into release-21.0 Jul 25, 2025
199 of 202 checks passed
@dbussink dbussink deleted the backport-18475-to-release-21.0 branch July 25, 2025 11:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant