Skip to content

Fix wp db repair --verbose test for MariaDB #336

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.

Sign up for GitHub

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

Merged
schlessera merged 2 commits into from
Jul 21, 2026
Merged

Fix wp db repair --verbose test for MariaDB #336

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
fb72073
Fix `wp db repair --verbose` test for MariaDB
schlessera Jul 21, 2026
2bdc4c4
Merge branch 'main' into fix/db-repair-verbose-mariadb-335
schlessera Jul 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 9 additions & 5 deletions features/db.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -181,14 +181,18 @@ Feature: Perform database operations
"""
And STDOUT should be empty

# Verbose option prints to STDERR.
When I try `wp db repair --verbose`
# `--verbose` makes the check command print progress information. MySQL's
# mysqlcheck writes "# Connecting to ..." to STDERR at a single --verbose,
# while MariaDB's mariadb-check writes "Processing databases" to STDOUT and
# only prints connection information at a higher verbosity. Merge the streams
# and accept either client's marker.
When I try `wp db repair --verbose 2>&1`
Then the return code should be 0
And STDERR should contain:
And STDOUT should match /(?:# Connecting to |Processing databases)/
And STDOUT should contain:
"""
Connecting
Success: Database repaired.
"""
And STDOUT should not be empty

@skip-sqlite
Scenario: db repair with --quiet flag should only show errors
Expand Down
Loading