Circleci test failures (apparently in waiting for project to come up)

[rfay]

What happened (or feature request):

We have regular test failures, apparently waiting for containers to become ready, which result in test timeouts and horrible huge stack traces. See https://circleci.com/gh/rfay/ddev/368?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link

Taking a look at the stack traces, this seems to happen in TestDescribe and TestRouterPortsCheck quite a lot.

Theories:

• The wait for container is too complex and can be simplified?
• We're running too many sites at once and should be turning them down after bringing them up?

What you expected to happen:

How to reproduce this:

Version: Please include the output of ddev version, docker version and the project's .ddev/config.yaml.

Anything else do we need to know:

Related source links or issues:

Please use a complexity rating of 1-5 (5 is high) for a feature request. (High complexity implies more PR planning)

[rfay]

I think there are probably two levels of failure here.

1. Site is not coming up. May be that we're using too many resources or...
2. EnsureHTTPStatus() is way more complex that it needs to be (there's a much simpler golang paradigm). The result is a huge (and late) failure.

This just needs some love, and probably needs some love pretty soon.