Fix MySQL container issue in Playwright E2E tests #2544
Closed
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.
Related to #2543
Implements health checks and logging for MySQL container and updates GitHub Actions workflows to ensure E2E tests pass without MySQL container issues.
compose.yml
to ensure it's fully operational before proceeding with tests. Also, updates logging options to capture more detailed information for debugging purposes.playwright.config.ts
to check the health of the MySQL container and ensure connectivity. Adjusts thewebServer
configuration to wait for the MySQL container to be fully operational before starting tests.playwright_admin.yml
,playwright_selfhost.yml
,playwright_visitor.yml
) to include a step for logging the status of the MySQL container before running tests. This step aims to provide insights into the MySQL container's state, aiding in troubleshooting and ensuring test reliability.For more details, open the Copilot Workspace session.