You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Michael Shuler (JIRA)" <ji...@apache.org> on 2016/07/11 15:55:11 UTC

[jira] [Commented] (CASSANDRA-9320) test-burn target should be run occasionally

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

Michael Shuler commented on CASSANDRA-9320:
-------------------------------------------

Been attempting this on ASF's Jenkins
https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-test-burn/

> test-burn target should be run occasionally
> -------------------------------------------
>
>                 Key: CASSANDRA-9320
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9320
>             Project: Cassandra
>          Issue Type: Test
>            Reporter: Ariel Weisberg
>            Assignee: Michael Shuler
>            Priority: Minor
>             Fix For: 3.x
>
>
> The tests are all concurrency tests right now so they need to run on the largest  # of cores we have available. The tests are not configured to run very long right now, but the intent is that they run for longer periods (days even).
> They aren't described as high value right now because the code under test hasn't change since first introduced so we can defer setting this job up until higher priority things are done.
> I think we should still run them at some low frequency so they don't rot or some change doesn't sneak in that effects them.



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