[
https://issues.apache.org/jira/browse/CASSANDRA-10451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14945579#comment-14945579
]
Paulo Motta commented on CASSANDRA-10451:
-----------------------------------------
Created [dtest PR|https://github.com/riptano/cassandra-dtest/pull/583] with
fixes. Basically ccm/dtest merges system.log and debug.log, so info/warn/error
statements are duplicated. Modified tests to only assert logs are present, and
not count them.
> Fix
> batch_test.TestBatch.logged_batch_gcgs_below_threshold_{multi,single}_table_test
> on CassCI
> ----------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-10451
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10451
> Project: Cassandra
> Issue Type: Sub-task
> Reporter: Jim Witschey
> Assignee: Paulo Motta
> Fix For: 3.0.0 rc2
>
>
> This is a recent regression:
> http://cassci.datastax.com/view/trunk/job/trunk_dtest/lastCompletedBuild/testReport/batch_test/TestBatch/logged_batch_gcgs_below_threshold_multi_table_test/history/
> Based on [when it started
> failing|http://cassci.datastax.com/view/trunk/job/trunk_dtest/623/changes],
> it looks like the regression was introduced by [the recent logging
> changes|https://github.com/apache/cassandra/commit/4a849efeb7c7c1a54bc12094d2d6a9f3f008a2fa].
> Pinging [~blerer] and [~pauloricardomg] to have a look.
> My initial guess was that the logs the test depends on were moved to the new
> debug log. However, the tests passes when I run it manually on openstack, so
> it could just be a configuration issue on CassCI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
