[
https://issues.apache.org/jira/browse/CASSANDRA-14648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16582672#comment-16582672
]
Benedict commented on CASSANDRA-14648:
--------------------------------------
Yes, that's also a good point. We could make the test serial.
If the tests were set to run serially (which can be configured in the CircleCI
yaml), it should create a test graph - and you should be able to click on the
bits of the graph and tell it to run those parts. I've not as-yet tried this
for a sequence of not-run pieces, but I am happy to confirm if it works.
> CircleCI dtest runs should (by default) depend upon successful unit tests
> -------------------------------------------------------------------------
>
> Key: CASSANDRA-14648
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14648
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Benedict
> Assignee: Benedict
> Priority: Major
>
> Unit tests are very quick to run, and if they fail to pass there’s probably
> no value in running dtests - particularly if we are honouring our
> expectations of never committing code that breaks either unit or dtests.
> When sharing CircleCI resources between multiple branches (or multiple
> users), it is wasteful to have two dtest runs kicked off for every incomplete
> branch that is pushed to GitHub for safe keeping. So I think a better
> default CircleCI config file would only run the dtests after a successful
> unit test run, and those who want to modify this behaviour can do so
> consciously by editing the config file for themselves.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
