[
https://issues.apache.org/jira/browse/CASSANDRA-16405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17274271#comment-17274271
]
Tomasz Lasica commented on CASSANDRA-16405:
-------------------------------------------
[https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch-dtest/358/#showFailuresLink]
on 2.2 shows 64 failures,
but I suspect this is known failure with 2.2 right now:
[https://ci-cassandra.apache.org/job/Cassandra-2.2/41/#showFailuresLink] (192
failures = 64 failures x 3 configurations probably)
> Handle both TimeoutError and NodeError when expecting node start failure
> ------------------------------------------------------------------------
>
> Key: CASSANDRA-16405
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16405
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/dtest/python
> Reporter: Tomasz Lasica
> Assignee: Tomasz Lasica
> Priority: Low
> Fix For: 2.2.x, 3.0.x, 3.11.x, 4.0-beta
>
>
> *Summary*
> Some tests are validating situation, when node (or cluster) does not start
> correctly.
> They rely on `TimeoutError` to be raised, but technically it is also possible
> that `ccm` will raise `NodeError` without waiting for timeout to be met.
> *Why we need this change*
> We can improve `ccm` to fail fast in case node being started terminates. This
> would:
> * make unexpected test failures faster to fail (not waiting 90 or 120s)
> * shorten overall test duration, even if timeout is given
> ccm work (in progress): [https://github.com/riptano/ccm/pull/724]
> *Proposed improvement*
> Handle both TimeoutError and NodeError as expected node failure.
> *PR*
> https://github.com/apache/cassandra-dtest/pull/120
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
