ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pavel Tupitsyn <ptupit...@apache.org>
Subject Re: .NET Long Running Test execution timeout
Date Mon, 05 Mar 2018 16:09:54 GMT
Hi Dmitry,

This test has been there forever. It checks that Ignite can start with
default config.
I think this is quite useful. TeamCity should be fixed to isolate
environments properly.

For now I've disabled the test with comment in master branch.

Thanks,
Pavel



On Mon, Mar 5, 2018 at 5:53 PM, Igor Sapego <isapego@apache.org> wrote:

> In C++ there are no tests that use TcpDiscoveryMulticastIpFinder. There
> are examples, though, that use it. As far as I know, currently all examples
> use TcpDiscoveryMulticastIpFinder, and there were some objections
> against using VmIpFinder instead.
>
> Am I right, folks?
>
> Best Regards,
> Igor
>
> On Mon, Mar 5, 2018 at 4:05 PM, Dmitry Pavlov <dpavlov.spb@gmail.com>
> wrote:
>
>> Hi Pavel, Igniters,
>>
>> There is new TC failure from .NET tests. Issue link:
>> https://issues.apache.org/jira/browse/IGNITE-7878
>>
>> Thanks to V.Ozerov we have located it is because usage
>> of TcpDiscoveryMulticastIpFinder. Probably there is some other Ignite node
>> running on other agents. Folks from infrastructure probably will fix
>> isolation of agents in future.
>>
>> But we need fast fix, it could be usage of VmIpFinder. Could you please
>> change configuration in tests? I personally prefer this change instead of
>> removal suite from RunAll. Currently these timeouts creates bottleneck in
>> win. agents and all Run-Alls waits .NET & CPP tests.
>>
>> Sincerely,
>> Dmitriy Pavlov
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message