cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ariel Weisberg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9717) TestCommitLog segment size dtests fail on trunk
Date Tue, 28 Jul 2015 19:24:04 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-9717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644886#comment-14644886
] 

Ariel Weisberg commented on CASSANDRA-9717:
-------------------------------------------

Maybe in 3.0 varint is having an impact? It's had a big impact on sizes in other tests.

The entire test is just to make sure segment size settings work? Looks like it does that to
me. +1

> 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)

Mime
View raw message