You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stefan Miklosovic (Jira)" <ji...@apache.org> on 2021/09/06 09:47:00 UTC
[jira] [Comment Edited] (CASSANDRA-14443) Improvements for running
dtests
[ https://issues.apache.org/jira/browse/CASSANDRA-14443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17410499#comment-17410499 ]
Stefan Miklosovic edited comment on CASSANDRA-14443 at 9/6/21, 9:46 AM:
------------------------------------------------------------------------
I dont think this is relevant anymore, is it?
For example, to run only upgrade tests:
pytest -vv --log-cli-level=DEBUG --junit-xml=nosetests.xml --junit-prefix=dtest-upgrade -s --cassandra-dir=/home/smiklosovic/dev/cassandra/cassandra-instaclustr/cassandra-3.0 --execute-upgrade-tests-only --upgrade-target-version-only --keep-failed-test-dir --upgrade-version-selection all
there is also "--only-resource-intensive-tests" as of current trunk.
was (Author: stefan.miklosovic):
I dont think this is relevant anymore, is it?
For example, to run only upgrade tests:
pytest -vv --log-cli-level=DEBUG --junit-xml=nosetests.xml --junit-prefix=dtest-upgrade -s --cassandra-dir=/home/smiklosovic/dev/cassandra/cassandra-instaclustr/cassandra-3.0 --execute-upgrade-tests-only --upgrade-target-version-only --keep-failed-test-dir --upgrade-version-selection all
there is also "--only-resource-intensive-tests" as of current trunk.
EDIT:
> Improvements for running dtests
> -------------------------------
>
> Key: CASSANDRA-14443
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14443
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/dtest/python
> Reporter: Kurt Greaves
> Assignee: Kurt Greaves
> Priority: Normal
> 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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org