On Wed, Sep 16, 2015 at 9:01 AM, Denis Magda <
[hidden email]> wrote:
> The tests keep failing. It means that Alex's changes don't correlate with
> an issue I'm observing in ignite-801.
>
> Put the latest info in [1]
>
Thanks Denis. Let's tackle this ticket in 1.5 release.
>
> --
> Denis
>
>
> On 9/16/2015 8:55 AM, Denis Magda wrote:
>
>> The ticket already exists [1]
>>
>> I've merged the latest changes from ignite-1.4 that should contain the
>> latest Alex's fixes and running the tests for now.
>>
>> Will send an update shortly.
>>
>> --
>> Denis
>>
>> [1]
https://issues.apache.org/jira/browse/IGNITE-801>>
>> On 9/16/2015 8:43 AM, Alexey Goncharuk wrote:
>>
>>> I did not check those particular tests after both ignite-264 and
>>> ignite-1482 were fixed. There might be something else left to fix, I will
>>> check the tests tomorrow and will create an additional ticket with proper
>>> description if something comes up.
>>>
>>> 2015-09-15 21:10 GMT-07:00 Dmitriy Setrakyan <
[hidden email]>:
>>>
>>> Igniters,
>>>>
>>>> I have come across IGNITE-1482 [1] which we have fixed in the upcoming
>>>> 1.4
>>>> release. The issue we have fixed had to do with IgniteCache.replace(...)
>>>> operation not returning a correct value on cluster topology changes.
>>>>
>>>> But a comment in the ticket states that data structures, like
>>>> AtomicLong,
>>>> AtomicSequence, etc., may suffer from the same problem. If that is the
>>>> case, have we fixed this issue for the data structures as well? If not,
>>>> we
>>>> should probably create a new ticket for it and cross-link these 2
>>>> issues
>>>> in Jira together.
>>>>
>>>> [1]
https://issues.apache.org/jira/browse/IGNITE-1482>>>>
>>>> D.
>>>>
>>>>
>>
>
Locked
