...and we're back!
On Tue, Apr 3, 2018 at 8:10 AM, shane knapp wrote:
> this apparently caused jenkins to get wedged overnight. i'll restarting
> it now.
>
> On Mon, Apr 2, 2018 at 9:12 PM, shane knapp wrote:
>
>> the problem was identified and fixed, and we should be good as of about
>> an ho
this apparently caused jenkins to get wedged overnight. i'll restarting it
now.
On Mon, Apr 2, 2018 at 9:12 PM, shane knapp wrote:
> the problem was identified and fixed, and we should be good as of about an
> hour ago.
>
> sorry for any inconvenience!
>
> On Mon, Apr 2, 2018 at 4:15 PM, shane
Thanks Shane for taking care of this!
On Mon, Apr 2, 2018 at 9:12 PM shane knapp wrote:
> the problem was identified and fixed, and we should be good as of about an
> hour ago.
>
> sorry for any inconvenience!
>
> On Mon, Apr 2, 2018 at 4:15 PM, shane knapp wrote:
>
>> hey all!
>>
>> we're havi
the problem was identified and fixed, and we should be good as of about an
hour ago.
sorry for any inconvenience!
On Mon, Apr 2, 2018 at 4:15 PM, shane knapp wrote:
> hey all!
>
> we're having network issues on campus right now, and the jenkins workers
> are experiencing up to 40% packet loss o
hey all!
we're having network issues on campus right now, and the jenkins workers
are experiencing up to 40% packet loss on our pings to github.
this can cause builds to time out when attempting to git fetch.
i'll post an update on the network status when i find out more about what's
going on.
