Skip to content

Fix correct tag values for MySQL Percona Server #20529

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

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

dujuku
Copy link

@dujuku dujuku commented Jun 17, 2025

What does this PR do?

Adds support and test scaffolding for Percona Server. This is an initial foundation to make further changes on, but there is a public change in the new query for the @@version_comment variable which is used to indicate whether the server is running a Percona build. This will be visible in tags.

Motivation

Review checklist (to be filled by reviewers)

  • Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
  • Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
  • If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

fix most tests for percona

fix final test
Copy link

codecov bot commented Jun 17, 2025

Codecov Report

Attention: Patch coverage is 88.88889% with 5 lines in your changes missing coverage. Please review.

Project coverage is 89.34%. Comparing base (10dda62) to head (ca003b7).

Additional details and impacted files
Flag Coverage Δ
activemq ?
cassandra ?
confluent_platform ?
hive ?
hivemq ?
hudi ?
ignite ?
jboss_wildfly ?
kafka ?
mysql 89.29% <88.88%> (-0.04%) ⬇️
presto ?
solr ?
tomcat ?
weblogic ?

Flags with carried forward coverage won't be shown. Click here to find out more.

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

Comment on lines +35 to +41
actual_payload["tables"].sort(key=lambda x: x["name"])
for table in actual_payload['tables']:
table['create_time'] = "normalized_value"
if 'columns' in table:
table['columns'].sort(key=lambda x: x['name'])
if 'indexes' in table:
table['indexes'].sort(key=lambda x: x['name'])
Copy link
Author

Choose a reason for hiding this comment

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

Adding the sorting here due to flaky tests. I think the only time ordering will matter is in the case of columns, but they have an ordinal_position field, so deterministic ordering in the payload should be unnecessary.

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