Done in rev. 1763453
Jacopo
On Wed, Oct 5, 2016 at 6:22 PM, Jacopo Cappellato <
[hidden email]> wrote:
> Oh yes, that is trivial.
>
> Jacopo
>
> On Wed, Oct 5, 2016 at 5:22 PM, Jacques Le Roux <
>
[hidden email]> wrote:
>
>> Yes I know Jacopo :)
>>
>> That was not my question. Could we not avoid to have this in error log?
>>
>> It's confusing, I already foresee users asking questions about that.
>>
>> Thanks
>>
>> Jacques
>>
>>
>>
>> Le 05/10/2016 à 11:41, Jacopo Cappellato a écrit :
>>
>>> This is a side effect of one of the new unit tests that is testing the
>>> behavior of the system when an invalid delegator name is used; you can
>>> safely ignore the message.
>>>
>>> Jacopo
>>>
>>> On Wed, Oct 5, 2016 at 2:27 PM, Jacques Le Roux <
>>>
[hidden email]> wrote:
>>>
>>> Hi,
>>>>
>>>> Is it normal that we see Test worker "errors" (false JUnit errors
>>>> actually, just tests) like
>>>>
>>>> 2016-10-04 09:58:47,590 |Test worker |DelegatorFactoryImpl |E|
>>>> Error creating delegator: No configuration found for delegator
>>>> [delegatorNameWithNoConfiguration]
>>>>
>>>> in the error.log. Should this not be only put in the console, does it
>>>> depends on Gradle?
>>>>
>>>> Thanks
>>>>
>>>> Jacques
>>>>
>>>>
>>>>
>>
>
Locked
