test: stop testing TestDdevFullSiteSetup on Windows/Colima [skip ci] #5041
Conversation
This file contains 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
|
Interestingly enough, https://buildkite.com/ddev/ddev-windows-mutagen/builds/4090#01890347-bfd6-4bba-808d-fc93bf430a6c also failed in TestDdevFullSiteSetup on a different test runner. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The Issue
Traditional Windows and Colima testing are very slow and TestDdevFullSiteSetup is particularly problematic with both.
How This PR Solves The Issue
We don't need TestDdevFullSiteSetup on Windows/Colima. Stop testing it
Future:
For ddevapp package, we could easily change the TestMain to skip certain tests automatically based on some general criteria instead of doing one-off changes like this.