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/10/06 18:25:26 UTC
[jira] [Created] (CASSANDRA-10451) Fix
batch_test.TestBatch.logged_batch_gcgs_below_threshold_multi_table_test on
CassCI
Jim Witschey created CASSANDRA-10451:
----------------------------------------
Summary: Fix batch_test.TestBatch.logged_batch_gcgs_below_threshold_multi_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
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)