Dmitriy, to my knowledge, the test will be fixed by the ticket
https://issues.apache.org/jira/browse/IGNITE-9550, we expect it to be
merged by the end of this week.

ср, 3 окт. 2018 г. в 18:00, Dmitriy Pavlov <dpavlov....@gmail.com>:

> Hi Alexey,
>
> Could you please assist with fixing test?
>
> Sincerely,
> Dmitriy Pavlov
>
> сб, 29 сент. 2018 г. в 12:23, Dmitriy Pavlov <dpavlov....@gmail.com>:
>
>> Folks,
>>
>> both tests are failed in ignite-2.7 IgniteStandByClusterTest.testSimple
>> <https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=1332314705000986815&branch=ignite-2.7&tab=testDetails>
>>  &
>> IgniteChangeGlobalStateFailOverTest.testActivateDeActivateOnFixTopologyWithPutValues
>> <https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-8427837226712025910&branch=ignite-2.7&tab=testDetails>
>>
>>
>> Can I hope these failures will be fixed in master and 2.7 before release?
>>
>> https://issues.apache.org/jira/browse/IGNITE-7618
>> <https://issues.apache.org/jira/browse/IGNITE-7618?focusedCommentId=16506923&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16506923>
>>
>>
>>
>> пт, 21 сент. 2018 г. в 11:33, Dmitrii Ryabov <somefire...@gmail.com>:
>>
>>> Hi, Dmitriy,
>>> I checked 7618 and previous commits: test fails locally starting from
>>> 7618.
>>> It fails because `cache.get()` remembers deactivated state and doesn't
>>> check current state.
>>>
>>> 2018-09-20 18:41 GMT+03:00 Dmitriy Pavlov <dpavlov....@gmail.com>:
>>>
>>> > Hi,
>>> >
>>> > IgniteStandByClusterTest seems to fail, Dmitriy G., Ivan, would it be
>>> > reasonable to revert commit?
>>> >
>>> > Dmitriy Ryabov, is it related to recent fix or is it a standalone
>>> problem?
>>> >
>>> > Sincerely,
>>> > Dmitriy Pavlov
>>> >
>>> > пн, 17 сент. 2018 г. в 18:45, Dmitrii Ryabov <somefire...@gmail.com>:
>>> >
>>> > > Looks like problem I had described in the ticket.
>>> > >
>>> > >
>>> > > https://issues.apache.org/jira/browse/IGNITE-7618?
>>> > focusedCommentId=16506923&page=com.atlassian.jira.
>>> > plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16506923
>>> > >
>>> > > 2018-09-15 12:01 GMT+03:00 Dmitriy Pavlov <dpavlov....@gmail.com>:
>>> > >
>>> > > > Dmitriy G, Ivan B,
>>> > > >
>>> > > > could you please double-check if failure is not coming from
>>> > > > https://issues.apache.org/jira/browse/IGNITE-7618
>>> > > >
>>> > > > Sincerely,
>>> > > > Dmitriy Pavlov
>>> > > >
>>> > > > сб, 15 сент. 2018 г. в 5:42, <dpavlov.ta...@gmail.com>:
>>> > > >
>>> > > > > Hi Ignite Developer,
>>> > > > >
>>> > > > > I am MTCGA.Bot, and I've detected some issue on TeamCity to be
>>> > > addressed.
>>> > > > > I hope you can help.
>>> > > > >
>>> > > > >  *    New test failure in master
>>> IgniteStandByClusterTest.testSimple
>>> > > > > https://ci.ignite.apache.org/project.html?projectId=
>>> > > > IgniteTests24Java8&testNameId=1332314705000986815&branch=%
>>> > > > 3Cdefault%3E&tab=testDetails
>>> > > > >  Changes may led to failure were done by
>>> > > > >          - bessonov.ip
>>> > > > > http://ci.ignite.apache.org/viewModification.html?modId=
>>> > > > 831651&personal=false
>>> > > > >
>>> > > > >         - If your changes can led to this failure(s), please
>>> create
>>> > > issue
>>> > > > > with label MakeTeamCityGreenAgain and assign it to you.
>>> > > > >         -- If you have fix, please set ticket to PA state and
>>> write
>>> > to
>>> > > > dev
>>> > > > > list fix is ready
>>> > > > >         -- For case fix will require some time please mute test
>>> and
>>> > set
>>> > > > > label Muted_Test to issue
>>> > > > >         - If you know which change caused failure please contact
>>> > change
>>> > > > > author directly
>>> > > > >         - If you don't know which change caused failure please
>>> send
>>> > > > > message to dev list to find out
>>> > > > > Should you have any questions please contact
>>> dev@ignite.apache.org
>>> > > > > Best Regards,
>>> > > > > MTCGA.Bot
>>> > > > > Notification generated at Sat Sep 15 05:42:21 MSK 2018
>>> > > > >
>>> > > >
>>> > >
>>> >
>>>
>>

Reply via email to