Skip to content

ci: fix misleading mysql57 label on ci-mysql84-g{1..5} check runs#5600

Merged
renecannao merged 1 commit intoGH-Actionsfrom
ci/fix-mysql84-infradb-label
Apr 11, 2026
Merged

ci: fix misleading mysql57 label on ci-mysql84-g{1..5} check runs#5600
renecannao merged 1 commit intoGH-Actionsfrom
ci/fix-mysql84-infradb-label

Conversation

@renecannao
Copy link
Copy Markdown
Contributor

@renecannao renecannao commented Apr 11, 2026

Summary

Five one-line fixes: `infradb: [ 'mysql57' ]` → `infradb: [ 'mysql84' ]` in each of `ci-mysql84-g{1..5}.yml`.

Why

The five `ci-mysql84-g*.yml` reusables introduced in #5597 inherited `infradb: [ 'mysql57' ]` from the `ci-legacy-g4.yml` template I `sed`'d them from. That value is interpolated into `env.MATRIX`:

```yaml
env:
MATRIX: '(${{ matrix.infradb }})'
```

…and `env.MATRIX` is interpolated into the `LouisBrunner/checks-action` step's `name` field:

```yaml
name: '${{ github.workflow }} / ${{ github.job }} ${{ env.MATRIX }}'
```

So on a real mysql84-g3 run the PR UI would display the check as:

```
CI-mysql84-g3 / tests (mysql57) ← misleading
```

…even though the tests themselves are correctly running against `infra-mysql84`. The infrastructure resolution path is unaffected: `ensure-infras.bash` strips the `-gN` suffix from `TAP_GROUP=mysql84-g3` to get `BASE_GROUP=mysql84`, which resolves to `test/tap/groups/mysql84/infras.lst` which lists `infra-mysql84`. The backend is right — only the label was wrong.

Caught by

gemini-code-assist review on #5598 (their inline comment on the sibling-file-cutting documentation). I also updated the docs in a companion commit on #5598 to call out `matrix.infradb` explicitly in the checklist, so future contributors don't repeat the mistake.

Test plan

  • Merge this PR into `GH-Actions`.
  • On the next push/PR that kicks off the CI cascade, verify that the `CI-mysql84-g*` check runs in the PR UI display as `(mysql84)`, not `(mysql57)`.
  • Verify the runs themselves still succeed (this is a label-only change; no behaviour change).

Files

```
.github/workflows/ci-mysql84-g1.yml
.github/workflows/ci-mysql84-g2.yml
.github/workflows/ci-mysql84-g3.yml
.github/workflows/ci-mysql84-g4.yml
.github/workflows/ci-mysql84-g5.yml
```

Five files, one line changed in each, +5/-5 total.

Summary by CodeRabbit

  • Chores
    • Updated CI workflows to test against MySQL 8.4 instead of MySQL 5.7 across multiple job configurations.

The five ci-mysql84-g*.yml reusables introduced in #5597 inherited
`infradb: [ 'mysql57' ]` from ci-legacy-g4.yml as the sed template.
The `infradb` matrix value is interpolated into `env.MATRIX` and then
into the check-action step's `name` field, so the GitHub PR UI would
display check runs as `CI-mysql84-g3 / tests (mysql57)` even though
the tests themselves are correctly running against infra-mysql84.

The infrastructure resolution is unaffected -- `ensure-infras.bash`
strips the -gN suffix from TAP_GROUP=mysql84-g3 to get BASE_GROUP=mysql84,
which resolves to test/tap/groups/mysql84/infras.lst (infra-mysql84).
This is purely a display-name fix.

Set infradb to 'mysql84' in all five files so the check run name
matches the backend actually under test.

Caught by gemini-code-assist review on #5598.
@gemini-code-assist
Copy link
Copy Markdown

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Apr 11, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 54de5b28-607f-426e-b57a-125b0d90fbbc

📥 Commits

Reviewing files that changed from the base of the PR and between 1b3149e and 6bedcb0.

📒 Files selected for processing (5)
  • .github/workflows/ci-mysql84-g1.yml
  • .github/workflows/ci-mysql84-g2.yml
  • .github/workflows/ci-mysql84-g3.yml
  • .github/workflows/ci-mysql84-g4.yml
  • .github/workflows/ci-mysql84-g5.yml
📜 Recent review details
🔇 Additional comments (5)
.github/workflows/ci-mysql84-g3.yml (1)

19-19: Correct label alignment for check-run naming.

Line 19 now matches the mysql84 workflow/infra context, so env.MATRIX and the checks-action display name will be accurate.

.github/workflows/ci-mysql84-g5.yml (1)

19-19: Good fix for matrix/display consistency.

Line 19 correctly updates the matrix value to mysql84, aligning check-run labels with the actual mysql84 infra path.

.github/workflows/ci-mysql84-g2.yml (1)

19-19: Nice targeted correction.

Line 19 now reflects mysql84, so the check name suffix generated from matrix.infradb is no longer misleading.

.github/workflows/ci-mysql84-g1.yml (1)

19-19: Approved: matrix value now matches workflow target.

Updating Line 19 to mysql84 keeps the visible check-run label consistent with the actual mysql84 group execution.

.github/workflows/ci-mysql84-g4.yml (1)

19-19: Looks good — labeling now matches actual infra variant.

Line 19 correctly switches the matrix label to mysql84, which should resolve the misleading check-run naming.


📝 Walkthrough

Walkthrough

This PR updates five CI workflow files to change the test matrix from targeting MySQL 5.7 to MySQL 8.4. Each workflow file has one line modified to update the infrastructure database variant, with no changes to workflow logic, steps, or configuration.

Changes

Cohort / File(s) Summary
CI Workflow Matrix Updates
.github/workflows/ci-mysql84-g1.yml, ci-mysql84-g2.yml, ci-mysql84-g3.yml, ci-mysql84-g4.yml, ci-mysql84-g5.yml
Updated test matrix infradb value from mysql57 to mysql84 across all five workflows.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Poem

🐰 Five workflows hop with MySQL grace,
From version five-seven to eighty-four's place,
A single line tweak in each file so neat,
Makes testing infrastructure complete!

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: fixing misleading mysql57 labels in the ci-mysql84-g{1..5} workflow files by updating the infradb matrix value from mysql57 to mysql84.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch ci/fix-mysql84-infradb-label

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

renecannao added a commit that referenced this pull request Apr 11, 2026
Addresses review feedback on #5598:

1. Adds `matrix.infradb` to the "What a sibling differs in" checklist.
   Gemini-code-assist flagged it -- and it was also a real bug in the
   merged ci-mysql84-g{1..5}.yml files, fixed in the separate #5600.
   The doc now explains that `infradb` is cosmetic for routing but
   displayed in the PR UI via env.MATRIX, so leaving it at the template
   default creates a misleading "CI-mysql84-g3 / tests (mysql57)" label.

2. Updates the sed example in "Adding a new test group" to substitute
   the infradb string alongside the group name, so copy-pasting from
   the doc produces a correct file on the first try.

3. Adds `text` language tag to seven previously untyped fenced code
   blocks (ASCII diagrams, directory listings, plain-text output) to
   satisfy markdownlint MD040. CodeRabbit flagged these. The repo
   doesn't enforce markdownlint, but the tag is harmless and silences
   the bot for future contributors editing the doc.
@renecannao renecannao merged commit 2dda74d into GH-Actions Apr 11, 2026
1 check passed
@sonarqubecloud
Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant