You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jim Witschey (JIRA)" <ji...@apache.org> on 2015/08/10 20:57:45 UTC
[jira] [Commented] (CASSANDRA-9717) TestCommitLog segment size
dtests fail on trunk
[ https://issues.apache.org/jira/browse/CASSANDRA-9717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680557#comment-14680557 ]
Jim Witschey commented on CASSANDRA-9717:
-----------------------------------------
Ok, looks like both {{commitlog_test.py:TestCommitLog.small_segment_size_test}} and {{commitlog_test.py:TestCommitLog.stop_failure_policy_test}} flap badly on trunk: http://cassci.datastax.com/view/trunk/job/trunk_dtest/445/testReport/junit/commitlog_test/TestCommitLog/history/
> 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: Jim Witschey
> 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)