Skip to content

[release-23.0] Fix flaky tests (#18835)#18839

Merged
timvaillancourt merged 2 commits intorelease-23.0from
backport-18835-to-release-23.0
Nov 5, 2025
Merged

[release-23.0] Fix flaky tests (#18835)#18839
timvaillancourt merged 2 commits intorelease-23.0from
backport-18835-to-release-23.0

Conversation

@vitess-bot
Copy link
Copy Markdown
Contributor

@vitess-bot vitess-bot bot commented Oct 29, 2025

Description

This is a backport of #18835

Signed-off-by: Arthur Schreiber <arthur@planetscale.com>
@vitess-bot vitess-bot bot added the Backport This is a backport label Oct 29, 2025
@vitess-bot vitess-bot bot requested a review from mattlord as a code owner October 29, 2025 10:45
@vitess-bot vitess-bot bot added Component: General Changes throughout the code base Type: Testing labels Oct 29, 2025
@vitess-bot
Copy link
Copy Markdown
Contributor Author

vitess-bot bot commented Oct 29, 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.

@vitess-bot vitess-bot bot requested a review from arthurschreiber October 29, 2025 10:45
@github-actions github-actions bot added this to the v23.0.0 milestone Oct 29, 2025
@codecov
Copy link
Copy Markdown

codecov bot commented Oct 29, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.69%. Comparing base (681e555) to head (1eea9ba).
⚠️ Report is 4 commits behind head on release-23.0.

Additional details and impacted files
@@               Coverage Diff                @@
##           release-23.0   #18839      +/-   ##
================================================
- Coverage         69.70%   69.69%   -0.02%     
================================================
  Files              1606     1606              
  Lines            214516   214516              
================================================
- Hits             149535   149502      -33     
- Misses            64981    65014      +33     

☔ 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.

@timvaillancourt timvaillancourt self-requested a review October 29, 2025 13:51
This was referenced Oct 29, 2025
@systay systay modified the milestones: v23.0.0, v23.0.1 Nov 4, 2025
@timvaillancourt timvaillancourt enabled auto-merge (squash) November 5, 2025 15:12
@timvaillancourt timvaillancourt merged commit 4e3dc56 into release-23.0 Nov 5, 2025
103 of 105 checks passed
@timvaillancourt timvaillancourt deleted the backport-18835-to-release-23.0 branch November 5, 2025 16:07
jwangace pushed a commit to jwangace/vitess that referenced this pull request Feb 5, 2026
Signed-off-by: Arthur Schreiber <arthur@planetscale.com>
Co-authored-by: vitess-bot[bot] <108069721+vitess-bot[bot]@users.noreply.github.com>
Co-authored-by: Tim Vaillancourt <tim@timvaillancourt.com>
jwangace pushed a commit to jwangace/vitess that referenced this pull request Feb 5, 2026
Signed-off-by: Arthur Schreiber <arthur@planetscale.com>
Co-authored-by: vitess-bot[bot] <108069721+vitess-bot[bot]@users.noreply.github.com>
Co-authored-by: Tim Vaillancourt <tim@timvaillancourt.com>
Signed-off-by: Jun Wang <jun.wang@demonware.net>
jwangace pushed a commit to jwangace/vitess that referenced this pull request Feb 5, 2026
Signed-off-by: Arthur Schreiber <arthur@planetscale.com>
Co-authored-by: vitess-bot[bot] <108069721+vitess-bot[bot]@users.noreply.github.com>
Co-authored-by: Tim Vaillancourt <tim@timvaillancourt.com>
Signed-off-by: Jun Wang <jun.wang@demonware.net>
jwangace pushed a commit to jwangace/vitess that referenced this pull request Feb 5, 2026
Signed-off-by: Arthur Schreiber <arthur@planetscale.com>
Co-authored-by: vitess-bot[bot] <108069721+vitess-bot[bot]@users.noreply.github.com>
Co-authored-by: Tim Vaillancourt <tim@timvaillancourt.com>
Signed-off-by: Jun Wang <jun.wang@demonware.net>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Backport This is a backport Component: General Changes throughout the code base Type: Testing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants