-
-
Notifications
You must be signed in to change notification settings - Fork 585
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[tests only] Improve TestRouterPortsCheck random failure, limit use of TestNodeJSVersions #5020
Conversation
Download the artifacts for this pull request:
See Testing a PR |
TestProjectPortsOverride seems to have the exact same problem (Colima) likely for exact same reason. |
pkg/ddevapp/ddevapp_test.go
Outdated
}, | ||
} | ||
|
||
containerID, out, err := dockerutil.RunSimpleContainer(versionconstants.GetWebImage(), t.Name()+"occupyport", nil, []string{}, []string{}, []string{"testnfsmount" + ":/nfsmount"}, "", false, true, nil, portBinding) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This must have a dockerutil.WaitContainer() or equivalent
0519a35
to
2c37b01
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
The Issue
TestRouterPortsCheck fails often, especially on colima slow Github actions test
TestNodeJSVersions often fails due to upstream problems or network problems. Don't test it in most places.
How This PR Solves The Issue