Skip to content

[release-20.0] Fix flakiness in vtexplain unit test case. (#16159)#16168

Merged
frouioui merged 1 commit intorelease-20.0from
backport-16159-to-release-20.0
Jun 13, 2024
Merged

[release-20.0] Fix flakiness in vtexplain unit test case. (#16159)#16168
frouioui merged 1 commit intorelease-20.0from
backport-16159-to-release-20.0

Conversation

@vitess-bot
Copy link
Copy Markdown
Contributor

@vitess-bot vitess-bot bot commented Jun 13, 2024

Description

This is a backport of #16159

@vitess-bot vitess-bot bot added the Backport This is a backport label Jun 13, 2024
@vitess-bot vitess-bot bot requested a review from systay as a code owner June 13, 2024 16:40
@vitess-bot vitess-bot bot added the Component: vtexplain changes made to vtexplain code label Jun 13, 2024
@vitess-bot vitess-bot bot requested a review from harshit-gangal as a code owner June 13, 2024 16:40
@vitess-bot vitess-bot bot requested a review from arthurschreiber June 13, 2024 16:40
@vitess-bot
Copy link
Copy Markdown
Contributor Author

vitess-bot bot commented Jun 13, 2024

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 v20.0.0 milestone Jun 13, 2024
@codecov
Copy link
Copy Markdown

codecov bot commented Jun 13, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.55%. Comparing base (9f57ff8) to head (274e4bf).
Report is 1 commits behind head on release-20.0.

Additional details and impacted files
@@              Coverage Diff              @@
##           release-20.0   #16168   +/-   ##
=============================================
  Coverage         68.54%   68.55%           
=============================================
  Files              1541     1541           
  Lines            197628   197628           
=============================================
+ Hits             135457   135475   +18     
+ Misses            62171    62153   -18     

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

@frouioui frouioui merged commit d616ba1 into release-20.0 Jun 13, 2024
@frouioui frouioui deleted the backport-16159-to-release-20.0 branch June 13, 2024 17:37
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: vtexplain changes made to vtexplain code Type: Testing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant