On 17 February 2016 at 11:22, Assaf Muller wrote:
> On Wed, Feb 17, 2016 at 2:16 PM, Armando M. wrote:
> >
> >
> > On 17 February 2016 at 11:12, Armando M. wrote:
> >>
> >> Hi folks,
> >>
> >> It looks like something slipped in and how we got persistent failures on
> >> functional/fullstack job
On Wed, Feb 17, 2016 at 2:16 PM, Armando M. wrote:
>
>
> On 17 February 2016 at 11:12, Armando M. wrote:
>>
>> Hi folks,
>>
>> It looks like something slipped in and how we got persistent failures on
>> functional/fullstack jobs [1]. Has anyone triaged? I couldn't find anything
>> in [2].
>
>
> L
On 17 February 2016 at 11:12, Armando M. wrote:
> Hi folks,
>
> It looks like something slipped in and how we got persistent failures on
> functional/fullstack jobs [1]. Has anyone triaged? I couldn't find anything
> in [2].
>
Looks like [1] fixed it. Thanks Assaf.
Be safe outta there. It's a s
Hi folks,
It looks like something slipped in and how we got persistent failures on
functional/fullstack jobs [1]. Has anyone triaged? I couldn't find anything
in [2].
The effect for this: we can't merge anything until this gets resolved. Some
might argue this is not necessarily a bad thing...
Ch
