> On May 7, 2016, at 2:48 PM, L Walsh wrote:
>
> Douglas Bell wrote:
>> Alright, thanks. I was finally shown the right settings to increase the
>> timeout to 60 seconds, so this problem should hopefully disappear (or at
>> least be quite reduced).
>>
>
> Have those setting been implem
Douglas Bell wrote:
Alright, thanks. I was finally shown the right settings to increase the timeout
to 60 seconds, so this problem should hopefully disappear (or at least be quite
reduced).
Have those setting been implemented yet?
I got these on 2 different browsers this morning:
Douglas Bell wrote:
About when did this slowdown start? I'd like to know if it correlates to when
we started enabling Fastly caching.
The first type of this error I saw in my browsing history was
sometime on or after april 1st.
I can't see exact D&T's in my history, but one entr
Alright, thanks. I was finally shown the right settings to increase the timeout
to 60 seconds, so this problem should hopefully disappear (or at least be quite
reduced).
> On May 5, 2016, at 12:35 PM, Linda A. Walsh wrote:
>
> Douglas Bell wrote:
>>
>> About when did this slowdown start? I'd
> On May 4, 2016, at 2:51 PM, L Walsh wrote:
>
> Douglas Bell wrote:
>> Over the QA Hackathon, we added Fastly caching to the cpantesters. That
>> error appears when the cache can't access cpantesters itself to update its
>> cache. We're still trying to get everything figured out here.
>>
>>
Douglas Bell wrote:
Over the QA Hackathon, we added Fastly caching to the cpantesters. That error
appears when the cache can't access cpantesters itself to update its cache.
We're still trying to get everything figured out here.
Fastly does geocaching, so you get a local version faster. It cac
Over the QA Hackathon, we added Fastly caching to the cpantesters. That error
appears when the cache can't access cpantesters itself to update its cache.
We're still trying to get everything figured out here.
Fastly does geocaching, so you get a local version faster. It caches for about
an hour
When I am looking at a smoker's test, there are buttons for 'RAW' and
'BACK'. BACK has reliably taken me to the version matrix, showing me
highest module value for a given perl, and showing me all the tests
run w/latest module on what platform.
Starting a few months back, hitting that BACK butt
