Skip to content

[release-20.0] Improve the queries upgrade/downgrade CI workflow by using same test code version as binary (#16494)#16502

Merged
systay merged 5 commits intorelease-20.0from
backport-16494-to-release-20.0
Jul 31, 2024
Merged

[release-20.0] Improve the queries upgrade/downgrade CI workflow by using same test code version as binary (#16494)#16502
systay merged 5 commits intorelease-20.0from
backport-16494-to-release-20.0

Conversation

@vitess-bot
Copy link
Copy Markdown
Contributor

@vitess-bot vitess-bot bot commented Jul 30, 2024

Description

This is a backport of #16494

@vitess-bot vitess-bot bot added Backport This is a backport Component: Build/CI Merge Conflict Skip CI Skip CI actions from running Type: Enhancement Logical improvement (somewhere between a bug and feature) labels Jul 30, 2024
@vitess-bot
Copy link
Copy Markdown
Contributor Author

vitess-bot bot commented Jul 30, 2024

Hello @frouioui, there are conflicts in this backport.

Please address them in order to merge this Pull Request. You can execute the snippet below to reset your branch and resolve the conflict manually.

Make sure you replace origin by the name of the vitessio/vitess remote

git fetch --all
gh pr checkout 16502 -R vitessio/vitess
git reset --hard origin/release-20.0
git cherry-pick -m 1 b88c62f01377182518c12a32cbc025fd8b0848b6

@vitess-bot
Copy link
Copy Markdown
Contributor Author

vitess-bot bot commented Jul 30, 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.2 milestone Jul 30, 2024
@codecov
Copy link
Copy Markdown

codecov bot commented Jul 30, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.66%. Comparing base (5c29a05) to head (b53fb49).
Report is 2 commits behind head on release-20.0.

Additional details and impacted files
@@               Coverage Diff                @@
##           release-20.0   #16502      +/-   ##
================================================
+ Coverage         68.64%   68.66%   +0.02%     
================================================
  Files              1541     1541              
  Lines            197848   197865      +17     
================================================
+ Hits             135806   135863      +57     
+ Misses            62042    62002      -40     

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

@frouioui frouioui force-pushed the backport-16494-to-release-20.0 branch from 670f75c to d28e42a Compare July 30, 2024 10:02
@frouioui frouioui removed Skip CI Skip CI actions from running Merge Conflict labels Jul 30, 2024
@frouioui frouioui marked this pull request as ready for review July 30, 2024 10:02
@frouioui frouioui requested a review from systay as a code owner July 30, 2024 10:02
…code version as binary (#16494)

Signed-off-by: Florent Poinsard <florent.poinsard@outlook.fr>
@frouioui frouioui force-pushed the backport-16494-to-release-20.0 branch from d28e42a to 8b58820 Compare July 30, 2024 10:03
frouioui added 2 commits July 31, 2024 12:31
Signed-off-by: Florent Poinsard <florent.poinsard@outlook.fr>
Signed-off-by: Florent Poinsard <florent.poinsard@outlook.fr>
frouioui added 2 commits July 31, 2024 13:58
Signed-off-by: Florent Poinsard <florent.poinsard@outlook.fr>
Signed-off-by: Florent Poinsard <florent.poinsard@outlook.fr>
@systay systay merged commit 624978e into release-20.0 Jul 31, 2024
@systay systay deleted the backport-16494-to-release-20.0 branch July 31, 2024 07:26
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: Build/CI Type: Enhancement Logical improvement (somewhere between a bug and feature)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants