[
https://issues.apache.org/jira/browse/IGNITE-10806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Namrata Bhave updated IGNITE-10806:
-----------------------------------
Description:
{{Hi,}}
{{`*GridMessageCollectionTest.testMarshal->doTestMarshal*` from
`*IgniteBasicTestSuite*` fails with below error on *big endian platform*:}}
_{{[ERROR] testMarshal(org.apache.ignite.util.GridMessageCollectionTest) Time
elapsed: 0 s <<< FAILURE!}}_
_{{junit.framework.AssertionFailedError: expected:<115> but was:<29440>}}_
_{{at
org.apache.ignite.util.GridMessageCollectionTest.doTestMarshal(GridMessageCollectionTest.java:120)}}_
_{{at
org.apache.ignite.util.GridMessageCollectionTest.doTestMarshal(GridMessageCollectionTest.java:89)}}_
_{{at
org.apache.ignite.util.GridMessageCollectionTest.testMarshal(GridMessageCollectionTest.java:71)}}_
{{As per my analysis, this error occurs when proto is set to 1 in
[GridMessageCollectionTest.java|#L74}}{{] and test passes for proto=2.}}
While checking the implementation of
[DirectByteBufferStreamImplV2.java|#L1422}}{{], observed write/read methods are
defined based on endianness and hence test passes for proto=2. I tried making
those changes in DirectByteBufferStreamImplV1.java(for proto=1) and test
passed.
I am not aware about the differences in the two protocol versions and their
implementation. Can the changes based on endianness be incorporated in v1 as
well? Could someone please help to resolve this?
was:
{{Hi,}}
{{`*GridMessageCollectionTest.testMarshal->doTestMarshal*` from
`*IgniteBasicTestSuite*` fails with below error on *big endian platform*:}}
_{{[ERROR] testMarshal(org.apache.ignite.util.GridMessageCollectionTest) Time
elapsed: 0 s <<< FAILURE!}}_
_{{junit.framework.AssertionFailedError: expected:<115> but was:<29440>}}_
_{{at
org.apache.ignite.util.GridMessageCollectionTest.doTestMarshal(GridMessageCollectionTest.java:120)}}_
_{{at
org.apache.ignite.util.GridMessageCollectionTest.doTestMarshal(GridMessageCollectionTest.java:89)}}_
_{{at
org.apache.ignite.util.GridMessageCollectionTest.testMarshal(GridMessageCollectionTest.java:71)}}_
{{As per my analysis, this error occurs when proto is set to 1 in
[GridMessageCollectionTest.java|}}{{https://github.com/apache/ignite/blob/2.7.0/modules/core/src/test/java/org/apache/ignite/util/GridMessageCollectionTest.java#L74}}{{]
and test passes for proto=2.}}
{{While checking the implementation of
[DirectByteBufferStreamImplV2.java|}}{{https://github.com/apache/ignite/blob/2.7.0/modules/core/src/main/java/org/apache/ignite/internal/direct/stream/v2/DirectByteBufferStreamImplV2.java#L1422}}{{],
observed write/read methods are defined based on endianness and hence test
passes for proto=2. I tried making those changes in
DirectByteBufferStreamImplV1.java(for proto=1) and test passed. }}
{{I am not aware about the differences in the two protocol versions and their
implementation. Can the changes based on endianness be incorporated in v1 as
well? Could someone please help to resolve this? }}
> Test failure on Big Endian
> --------------------------
>
> Key: IGNITE-10806
> URL: https://issues.apache.org/jira/browse/IGNITE-10806
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.6, 2.7
> Environment: Linux Ubuntu 16.04 Big Endian
> Reporter: Namrata Bhave
> Priority: Major
>
> {{Hi,}}
> {{`*GridMessageCollectionTest.testMarshal->doTestMarshal*` from
> `*IgniteBasicTestSuite*` fails with below error on *big endian platform*:}}
> _{{[ERROR] testMarshal(org.apache.ignite.util.GridMessageCollectionTest)
> Time elapsed: 0 s <<< FAILURE!}}_
> _{{junit.framework.AssertionFailedError: expected:<115> but was:<29440>}}_
> _{{at
> org.apache.ignite.util.GridMessageCollectionTest.doTestMarshal(GridMessageCollectionTest.java:120)}}_
> _{{at
> org.apache.ignite.util.GridMessageCollectionTest.doTestMarshal(GridMessageCollectionTest.java:89)}}_
> _{{at
> org.apache.ignite.util.GridMessageCollectionTest.testMarshal(GridMessageCollectionTest.java:71)}}_
> {{As per my analysis, this error occurs when proto is set to 1 in
> [GridMessageCollectionTest.java|#L74}}{{] and test passes for proto=2.}}
> While checking the implementation of
> [DirectByteBufferStreamImplV2.java|#L1422}}{{], observed write/read methods
> are defined based on endianness and hence test passes for proto=2. I tried
> making those changes in DirectByteBufferStreamImplV1.java(for proto=1) and
> test passed.
> I am not aware about the differences in the two protocol versions and their
> implementation. Can the changes based on endianness be incorporated in v1 as
> well? Could someone please help to resolve this?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
