[
https://issues.apache.org/jira/browse/IGNITE-12238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16941091#comment-16941091
]
Ignite TC Bot commented on IGNITE-12238:
----------------------------------------
{panel:title=Branch: [pull/6921/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4641839&buildTypeId=IgniteTests24Java8_RunAll]
> RobinHoodBackwardShiftHashMap works incorrectly on big endian architectures
> ---------------------------------------------------------------------------
>
> Key: IGNITE-12238
> URL: https://issues.apache.org/jira/browse/IGNITE-12238
> Project: Ignite
> Issue Type: Bug
> Reporter: Andrey N. Gura
> Assignee: Andrey N. Gura
> Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{RobinHoodBackwardShiftHashMap}} has bug that can be reproduced only on big
> endinan architectures. In order to reproduce the problem run the following
> tests:
> * {{RobinHoodBackwardShiftHashMapTest.testCollisionOnRemove}}
> * {{testRandomOpsPutRemove}}
> The problem is {{setIdealBucket()}} method writes {{long}} value to the
> offheap memory, while {{getIdealBucket()}} reads {{int}} value. For little
> endian architectures it works because meaningful 4 bytes will written first
> to the memory and leading zero bytes will be rewriteen by the next operation.
> On big endian architecture always 4 zero bytes will be written to the memory.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
