On 20/07/18 16:54, Daniel Farrell wrote:
>
> I feel like blaming infrastructure being "slow" is too easy an
> excuse for issues. If the software was run in a customer production
> environment I suspect telling the customer that their hardware is
> too slow and is not the same
On Fri, Jul 20, 2018 at 10:54 AM, Daniel Farrell
wrote:
> On Fri, Jul 20, 2018 at 10:36 AM Thanh Ha
> wrote:
>
>> On Fri, Jul 20, 2018 at 10:01 AM Tom Pantelis
>> wrote:
>>
>>> On Fri, Jul 20, 2018 at 4:48 AM, Anil Belur
>>> wrote:
>>>
On Fri, Jul 20, 2018 at 11:12 AM Jenkins >>>
On Fri, Jul 20, 2018 at 10:36 AM Thanh Ha
wrote:
> On Fri, Jul 20, 2018 at 10:01 AM Tom Pantelis
> wrote:
>
>> On Fri, Jul 20, 2018 at 4:48 AM, Anil Belur
>> wrote:
>>
>>> On Fri, Jul 20, 2018 at 11:12 AM Jenkins <
>>> jenkins-dontre...@opendaylight.org> wrote:
>>>
Attention
On Fri, Jul 20, 2018 at 10:01 AM Tom Pantelis wrote:
> On Fri, Jul 20, 2018 at 4:48 AM, Anil Belur
> wrote:
>
>> On Fri, Jul 20, 2018 at 11:12 AM Jenkins <
>> jenkins-dontre...@opendaylight.org> wrote:
>>
>>> Attention controller-devs,
>>>
>>> Autorelease oxygen failed to build
On Fri, Jul 20, 2018 at 4:48 AM, Anil Belur
wrote:
>
>
> On Fri, Jul 20, 2018 at 11:12 AM Jenkins opendaylight.org> wrote:
>
>> Attention controller-devs,
>>
>> Autorelease oxygen failed to build sal-cluster-admin-impl from controller
>> in build
>> 359. Attached is a snippet of the error
On Fri, Jul 20, 2018 at 11:12 AM Jenkins
wrote:
> Attention controller-devs,
>
> Autorelease oxygen failed to build sal-cluster-admin-impl from controller
> in build
> 359. Attached is a snippet of the error message related to the
> failure that we were able to automatically parse as well as
Attention controller-devs,
Autorelease oxygen failed to build sal-cluster-admin-impl from controller in
build
359. Attached is a snippet of the error message related to the
failure that we were able to automatically parse as well as console logs.
Console Logs:
