Github user PivotalSarge commented on the issue:
https://github.com/apache/geode-native/pull/44
The unit tests failed on Linux but not other platforms. It turns out that
DataOutput has some not-very-obvious (and apparently platform-specific)
behavior around buffer management that results in the return values from
getBufferLength() and getRemainingBufferLength() depending on the behavior of
other unit tests that may precede them. Hence, the test of ginormous query
strings was causing the return values of those methods to differ from what
would be returned if that test was *not* run. So I reworked how the DataOutput
cursor advancement unit tests work and created GEODE-2598 to understand and
test how DataOutput's buffer management works.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
