You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Carl Yeksigian (JIRA)" <ji...@apache.org> on 2015/11/12 20:51:11 UTC

[jira] [Updated] (CASSANDRA-10457) fix failing jmx_metrics dtest

     [ https://issues.apache.org/jira/browse/CASSANDRA-10457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carl Yeksigian updated CASSANDRA-10457:
---------------------------------------
    Fix Version/s:     (was: 2.2.x)
                   2.2.3

> fix failing jmx_metrics dtest
> -----------------------------
>
>                 Key: CASSANDRA-10457
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10457
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Jim Witschey
>            Assignee: Carl Yeksigian
>             Fix For: 2.2.3, 3.0.0 rc2
>
>
> {{jmxmetrics_test.py:TestJMXMetrics.begin_test}} is failing on CassCI; I've reproduced it on OpenStack as well. Here's the failure:
> http://cassci.datastax.com/view/trunk/job/cassandra-3.0_dtest/lastCompletedBuild/testReport/jmxmetrics_test/TestJMXMetrics/begin_test/
> My first thought is that a fix may be as simple as changing the parameters to stress between collecting the before and after metrics. I haven't debugged this further than reproducing it, though.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)