Give release builds more time.

Give release builds more time.

Lets see if this removes the flake on the bots seen in sky tests. In
local testing it looks like sky_server's CherryPy becomes overloaded and
then the requests take a very long time to complete which makes the tests
timeout. I increased the timeout locally and it made the tests start
passing consistently when using high --repeat values.

R=ojan@chromium.org

Committed: https://chromium.googlesource.com/external/mojo/+/cf873181ba11ee78b72796419fc2c3d7ec4b5555

[ojan, 2014-11-19 01:56:01]

lgtm

We should just move back to apache. I don't see what cherrypy is buying us here.

[abarth-chromium, 2014-11-19 02:03:27]

On 2014/11/19 at 01:56:01, ojan wrote:
> We should just move back to apache. I don't see what cherrypy is buying us
here.

That's fine with me.  Ideally we'd made skydb use apache too then.

[esprehn, 2014-11-19 02:03:39]

Committed patchset #1 (id:1) manually as
cf873181ba11ee78b72796419fc2c3d7ec4b5555 (presubmit successful).

[eseidel, 2014-11-19 03:17:22]

eseidel@chromium.org changed reviewers:
+ eseidel@chromium.org

[eseidel, 2014-11-19 03:17:22]

I'm not at all tied to cherrypy.  At the time it seemed simpler than writing yet
another httpd.conf file.

[ojan, 2014-11-19 06:32:45]

On 2014/11/19 03:17:22, eseidel wrote:
> I'm not at all tied to cherrypy.  At the time it seemed simpler than writing
yet
> another httpd.conf file.

I'm fine with sticking with cherrypy, but then someone needs to do work to make
it scale better, which seems like not a great use of our time. I'm not sure this
dream of having sky_server represent how we expect developers to use sky is
serving us well in the short-term (which is how abarth justified having the new
server to me). We might want that eventually, but in the short-term I feel like
it's just getting in the way. Which is to say, is there a reason not to just use
the same apache server and httpd.conf for both the tests and sky_server/skydb?

[eseidel, 2014-11-19 07:36:46]

Go for it! :)