[
https://issues.apache.org/jira/browse/CASSANDRA-17729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17563145#comment-17563145
]
Michael Semb Wever commented on CASSANDRA-17729:
------------------------------------------------
Agree with the notion that Jenkins (lower resources/more contention) is better
at exposing flakies, but that there's a trade-off between encouraging flakies
and creating difficult-to-deal-with noise.
While I'm for raising the discussion about what is the base hardware
requirement (once HDD issues are resolved and all agents are active again), I
don't see this as an argument not to continuously improve tests to be more
robust. So +1 to the patch.
> Raise test timeouts
> -------------------
>
> Key: CASSANDRA-17729
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17729
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
> Reporter: Berenguer Blasi
> Assignee: Berenguer Blasi
> Priority: Normal
> Fix For: 4.1-beta
>
>
> We have seen for some time now junits timeout frequently on jenkins. This is
> probably down to it being a very loaded env. On circle we don't observe that
> behavior probably bc it's not so loaded.
> The question is whether it is time to raise timeouts as they might be hiding
> legit failures. As en experiment I raised timeouts in a branch and ran
> jenkins against it. What I see is that the last 4.1 run had 14 failures out
> of which 12 were timeouts. Increasing timeouts reveals what looks to be 9
> legit failures where 2 are timeouts that probably need to be investigated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
