Build/Test Tools: Add a start period to the MySQL healthcheck.

[adimoldovan]

The mysql healthcheck sets interval, timeout, and retries, but not start_period. Docker therefore counts the checks that run while the database initializes against the retry budget of interval × retries, which is 50 seconds.

The first start of a database volume creates the data directory and runs the files in /docker-entrypoint-initdb.d. On a loaded CI runner that work can take longer than 50 seconds. Docker then marks the container unhealthy, every service that declares mysql: condition: service_healthy fails to start, and docker compose up fails:

09:33:37  Container wordpress-develop-mysql-1  Started
09:33:37  Container wordpress-develop-mysql-1  Waiting
09:34:27  Container wordpress-develop-mysql-1  Error
          dependency failed to start: container wordpress-develop-mysql-1 is unhealthy

Example run: https://github.com/WordPress/wordpress-develop/actions/runs/30439797855/job/90536164263

This patch adds start_period: 60s.

Testing instructions

The failure needs a first start that takes more than 50 seconds. A fast machine initializes the volume in about 10 seconds, so the failure does not appear locally. Measure the margin instead:

npm run env:stop
docker compose down -v
docker compose up -d mysql
docker inspect --format '{{.State.Health.Status}}' $(docker compose ps -q mysql)

Repeat the inspect command and record how long the container stays starting. Compare that time to the 50 second budget.

Then confirm that the start period does not delay a healthy start: on this branch the container still reports healthy at the same point it did before, not 60 seconds later.

Trac ticket: https://core.trac.wordpress.org/ticket/65752

---

This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

[Copilot]

Pull request overview

This PR improves the reliability of the local/CI Docker Compose environment by preventing MySQL healthcheck failures during initial database initialization, which can exceed the current interval × retries budget and cause dependent services to fail to start.

Changes:

• Add start_period: 60s to the mysql service healthcheck to avoid counting early failures against the retry streak during cold starts.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props adrianmoldovanwp.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

[lancewillett]

No blockers.

What I tested:

• Rendered the Compose config and confirmed MySQL receives start_period: 1m0s
• Confirmed dependent services still wait for service_healthy
• Reviewed the current diff and CI—all checks passed

[github-actions]

A commit was made that fixes the Trac ticket referenced in the description of this pull request.

SVN changeset: 62937
GitHub commit: 123f966

This PR will be closed, but please confirm the accuracy of this and reopen if there is more work to be done.