ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitry Pavlov <dpavlov....@gmail.com>
Subject Re: .NET Long Running Test execution timeout
Date Mon, 12 Mar 2018 13:30:03 GMT
Thank you! I'll start the builds later.

пн, 12 мар. 2018 г. в 16:23, Pavel Tupitsyn <ptupitsyn@apache.org>:

> Reverted that commit.
>
> On Mon, Mar 12, 2018 at 2:34 PM, Dmitry Pavlov <dpavlov.spb@gmail.com>
> wrote:
>
>> Hi Pavel,
>>
>> Thanks to Vitaliy Osipov multicast is prohibited on TeamCity agents,
>> there should no interference anymore.
>>
>> Could you please return test to code
>> (18c6b4a5d079874e9c156fa39564970ad3c31914) ?
>>
>> I'll check if issue https://issues.apache.org/jira/browse/IGNITE-7878
>> is reproducible and close ticket later.
>>
>> Sincerely,
>> Dmitriy Pavlov
>>
>> пн, 5 мар. 2018 г. в 19:14, Dmitry Pavlov <dpavlov.spb@gmail.com>:
>>
>>> Hi Pavel,
>>>
>>> Thank you!
>>>
>>> Let's wait for fix at TeamCity.
>>>
>>> Sincerely,
>>> Dmitriy Pavlov
>>>
>>> пн, 5 мар. 2018 г. в 19:09, Pavel Tupitsyn <ptupitsyn@apache.org>:
>>>
>>>> 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