You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Berenguer Blasi (Jira)" <ji...@apache.org> on 2022/07/05 04:36:00 UTC
[jira] [Updated] (CASSANDRA-17729) Raise test timeouts
[ https://issues.apache.org/jira/browse/CASSANDRA-17729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Berenguer Blasi updated CASSANDRA-17729:
----------------------------------------
Bug Category: Parent values: Degradation(12984)
Complexity: Normal
Discovered By: Unit Test
Fix Version/s: 4.1-beta
Severity: Normal
Status: Open (was: Triage Needed)
> 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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org