[
https://issues.apache.org/jira/browse/CASSANDRA-9717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14613119#comment-14613119
]
Branimir Lambov commented on CASSANDRA-9717:
--------------------------------------------
I suppose the easiest thing to do here is to increase the tolerance, but the
test can still be flaky after we do that. A better solution is to fix the
random seed for the writes so that we can use a small tolerance and avoid all
flakiness, but I don't know if that's something we can do with the dtest
infrastructure (or how, if we can).
> TestCommitLog segment size dtests fail on trunk
> -----------------------------------------------
>
> Key: CASSANDRA-9717
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9717
> Project: Cassandra
> Issue Type: Sub-task
> Reporter: Jim Witschey
> Assignee: Branimir Lambov
> Priority: Blocker
> Fix For: 3.0 beta 1
>
>
> The test for the commit log segment size when the specified size is 32MB. It
> fails for me locally and on on cassci. ([cassci
> link|http://cassci.datastax.com/view/trunk/job/trunk_dtest/305/testReport/commitlog_test/TestCommitLog/default_segment_size_test/])
> The command to run the test by itself is {{CASSANDRA_VERSION=git:trunk
> nosetests commitlog_test.py:TestCommitLog.default_segment_size_test}}.
> EDIT: a similar test,
> {{commitlog_test.py:TestCommitLog.small_segment_size_test}}, also fails with
> a similar error.
> The solution here may just be to change the expected size or the acceptable
> error -- the result isn't far off. I'm happy to make the dtest change if
> that's the solution.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
