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

Relax vexplain test for upcoming changes #17035

Merged

Conversation

dbussink
Copy link
Contributor

The fix in #16988 makes a change here that's not really a breaking change, but it does break the test as the test matches the exact string output which changes here due to a binary value.

Related Issue(s)

Needed for #16988 which is a fix for #16989.

Checklist

  • "Backport to:" labels have been added if this change should be back-ported to release branches
  • If this change is to be back-ported to previous releases, a justification is included in the PR description
  • Tests were added or are not required
  • Did the new or modified tests pass consistently locally and on CI?
  • Documentation was added or is not required

Copy link
Contributor

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

@vitess-bot vitess-bot bot added NeedsBackportReason If backport labels have been applied to a PR, a justification is required NeedsDescriptionUpdate The description is not clear or comprehensive enough, and needs work NeedsIssue A linked issue is missing for this Pull Request NeedsWebsiteDocsUpdate What it says labels Oct 22, 2024
@dbussink dbussink added Component: Query Serving Type: Testing and removed NeedsDescriptionUpdate The description is not clear or comprehensive enough, and needs work NeedsWebsiteDocsUpdate What it says NeedsIssue A linked issue is missing for this Pull Request NeedsBackportReason If backport labels have been applied to a PR, a justification is required labels Oct 22, 2024
@github-actions github-actions bot added this to the v21.0.0 milestone Oct 22, 2024
Copy link

codecov bot commented Oct 22, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 67.21%. Comparing base (1a3b5a1) to head (d114d07).
Report is 1 commits behind head on release-21.0.

Additional details and impacted files
@@              Coverage Diff              @@
##           release-21.0   #17035   +/-   ##
=============================================
  Coverage         67.21%   67.21%           
=============================================
  Files              1570     1570           
  Lines            251256   251256           
=============================================
+ Hits             168885   168890    +5     
+ Misses            82371    82366    -5     

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

The fix in vitessio#16988 makes a change
here that's not really a breaking change, but it does break the test as
the test matches the exact string output which changes here due to a
binary value.

Signed-off-by: Dirkjan Bussink <[email protected]>
@dbussink dbussink force-pushed the dbussink/relax-vexplain-test branch from 406e763 to 564cf1a Compare October 22, 2024 13:06
@@ -53,6 +53,7 @@ func start(t *testing.T) (*mysql.Conn, func()) {
}

func TestVtGateVExplain(t *testing.T) {
t.Skip("v22 changes the output of vexplain queries because of binary bind vars which breaks this test.")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is fine too, but we can also only skip for v22 version of vtgate.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I plan to clean this up / improve this once I have #16988 landed on main.

Signed-off-by: Dirkjan Bussink <[email protected]>
@rohit-nayak-ps rohit-nayak-ps merged commit ac11a8c into vitessio:release-21.0 Oct 22, 2024
97 of 98 checks passed
@rohit-nayak-ps rohit-nayak-ps deleted the dbussink/relax-vexplain-test branch October 22, 2024 16:30
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.

3 participants