[
https://issues.apache.org/jira/browse/GEODE-9885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479628#comment-17479628
]
Donal Evans commented on GEODE-9885:
------------------------------------
The test failures were due to Jedis client retrying automatically when an
APPEND operation failed due to a bucket moving, which occasionally led to the
APPEND being applied twice. The test has been modified to account for
occasional duplicated appends.
> StringsDUnitTest.givenBucketsMoveDuringAppend_thenDataIsNotLost fails with
> duplicated append
> --------------------------------------------------------------------------------------------
>
> Key: GEODE-9885
> URL: https://issues.apache.org/jira/browse/GEODE-9885
> Project: Geode
> Issue Type: Bug
> Components: redis
> Affects Versions: 1.15.0
> Reporter: Ray Ingles
> Assignee: Donal Evans
> Priority: Major
> Labels: needsTriage, pull-request-available
>
> The test appends a lot of strings to a key. It wound up adding (at least one)
> extra string to the stored string:
> {\{java.util.concurrent.ExecutionException: java.lang.AssertionError:
> unexpected -{append0}-key-3-27680 at index 27681 iterationCount=61995 in
> string}}
> The string "\{append0}-key-3-27680" appeared twice in sequence.
> Additional to this failure, the test should be modified to produce a more
> useful failure message. The current assertion prints the entire String upon
> failure, which can contain upwards of 50,000 repeats of the
> "\{append0}-key-3*" String, making the output large and unreadable. Consider
> using an assertion with {{.withFailureMessage()}} to produce a more useful
> error message rather than the currently used {{Assert.fail().}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
