[
https://issues.apache.org/jira/browse/CASSANDRA-14443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470217#comment-16470217
]
Kurt Greaves edited comment on CASSANDRA-14443 at 7/2/18 11:49 AM:
-------------------------------------------------------------------
[patch for
dtests|https://github.com/apache/cassandra-dtest/compare/master...kgreav:14443]
So I initially was only going to make that one small fix, but then I realised
we currently don't have a way to run _only_ the resource intensive tests, and I
ended up implementing a {{--resource-intensive-tests-only}} command... And then
I did the same for upgrade tests.
Seems that our jenkins tests will be doubling up on a lot of tests because the
"large" tests are running everything - not just resource-intensive. Once this
flag gets in we should use it for any "large" dtest runs.
was (Author: kurtg):
[patch for
dtests|https://github.com/apache/cassandra-dtest/compare/master...kgreav:remove_system_resource_check]
So I initially was only going to make that one small fix, but then I realised
we currently don't have a way to run _only_ the resource intensive tests, and I
ended up implementing a {{--resource-intensive-tests-only}} command... And then
I did the same for upgrade tests.
Seems that our jenkins tests will be doubling up on a lot of tests because the
"large" tests are running everything - not just resource-intensive. Once this
flag gets in we should use it for any "large" dtest runs.
> Improvements for running dtests
> -------------------------------
>
> Key: CASSANDRA-14443
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14443
> Project: Cassandra
> Issue Type: Improvement
> Components: Testing
> Reporter: Kurt Greaves
> Assignee: Kurt Greaves
> Priority: Major
> Labels: dtest
>
> We currently hardcode a requirement that you need at least 27gb of memory to
> run the resource intensive tests. This is rather annoying as there isn't
> really a strict hardware requirement and tests can run on smaller machines in
> a lot of cases (especially if you mess around with HEAP).
> We've already got the command line argument
> {{--force-resource-intensive-tests}}, we don't need additional restrictions
> in place to stop people who shouldn't be running the tests from running them.
> We also don't have a way to run _only_ the resource-intensive dtests or
> _only_ the upgrade tests
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
