Upon closer inspection, it looks like it's gotten worse today. I'm looking into it.
> On Aug 17, 2017, at 1:04 PM, Doug Bell <d...@preaction.me> wrote: > > Yes. Now that the incoming test reports are on the same machine as the rest > of the web APIs, they are now subject to the random, debilitating spikes in > traffic that everything else is. I can't ban everyone doing it, so I have to > fix the performance problems. This will take some time. > > If these came from earlier in the week (Saturday/Sunday), then it was a > misconfiguration of the Fastly proxy. The timeouts have been increased quite > a bit, but the traffic spikes still kill the server. > >> On Aug 17, 2017, at 6:34 AM, David Cantrell <da...@cantrell.org.uk> wrote: >> >> Yesterday evening and this morning I've been getting messages similar to >> this when I try to look at the test failures that I get in my mail: >> >> Error 503 first byte timeout >> first byte timeout >> Guru Mediation: >> Details: cache-lhr6336-LHR 1502969464 1081180210 >> Varnish cache server >> >> or >> >> Error 503 backend read error >> backend read error >> Guru Mediation: >> Details: cache-lhr6336-LHR 1502969525 1081782213 >> Varnish cache server >> >> I generally get what I wanted after a few retries though. >> >> -- >> David Cantrell | Bourgeois reactionary pig >> >> Hail Caesar! Those about to vi ^[ you!
