Repository navigation
Add Docker setup and container CI workflow for the test runner - #344
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. Unlinked AccountsThe following contributors have not linked their GitHub and WordPress.org accounts: @mindctrl, @jazzsequence. Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases. If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. Props Bot commandsYou can trigger Props Bot actions by commenting on this PR:
|
ekamran
left a comment
ekamran
left a comment
There was a problem hiding this comment.
Thanks @dhruvang21, this works well. I checked the CI results (25,956 tests on both jobs), ran the full compose setup on macOS arm64 (25,976 tests, 0 failures), and tried a database that never comes up and a failing prepare. Both stop with the right summary and exit code. The report workflow cannot run before merge, so I ran its script against mocks: it updates only its own comment, ignores a copied marker, neutralises mentions, skips symlinks, and finds the PR only from the run.
Small one, not blocking: line 13 of compose.yaml says any WPT_* variable can be passed through, but only the listed ones are. The README already says it right.
ekamran
left a comment
ekamran
left a comment
There was a problem hiding this comment.
Re-checked at bd841e0: the concurrency group now uses the PR number, and the compose healthcheck replaces the entrypoint wait. Locally the db service became healthy on mariadb:11.4 (through the mariadb-admin fallback), mariadb:10.6, mysql:8.4 and mysql:5.7 (amd64), and the container runs in CI pass on MySQL 8.4 and MariaDB 10.6. Thanks @dhruvang21.
Description
Run prepare, test, report, and cleanup in a container against a throwaway MySQL/MariaDB database. Save each step's log, junit.xml, env.json, and a Markdown summary to output/. See #274 (comment).
How bot report works: when Container Tests finishes for a PR, the bot downloads the results artifacts, combines each job's summary into one comment, and posts it on the PR. Later pushes update that same comment instead of adding new ones. If a run fails before uploading anything (for example, the image fails to build), the comment says so and links to the run. Cancelled runs are skipped.
Security