ci: add MySQL service to estate code-coverage job - #263
Merged
Conrad Rockenhaus (skyphusion) merged 1 commit intoAug 7, 2026
Conversation
The standalone code-coverage workflow ran vitest without a MySQL container, so DB-backed tests failed ECONNREFUSED 127.0.0.1:3306 while ci.yml coverage already had the service. Match ci.yml MySQL 8 setup so the required coverage check is real.
Adversarial security auditGenerated 2026-08-07T08:40:21.415Z · (no summary)
|
Conrad Rockenhaus (skyphusion)
deleted the
fix/code-coverage-mysql-service
branch
August 7, 2026 08:42
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
code-coverage.ymlhad no MySQL service; tests hitECONNREFUSED 127.0.0.1:3306ci.ymlMySQL 8 service + schema migrate beforetest:coverageWhy
Required check name
coveragecan come from this workflow; false reds blocked docs merges.