[ 
https://issues.apache.org/jira/browse/CASSANDRA-17729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17563574#comment-17563574
 ] 

Berenguer Blasi commented on CASSANDRA-17729:
---------------------------------------------

Through all the reviews and tests fixes I have done all this time there are 
plenty that will only repro on circle or only on jenkins, yes. And I think that 
is shared pov if you ask at least in my team.  It is common for me to be 
involved in tickets that only repro on jenkins. In fact the jenkins run in this 
ticket is showing a few that don't show on the matching circle run.

How this would relate to a 'properly' provisioned cluster, which we would have 
to define, I can't tell. I see your point right, bc there are some snakes in 
the grass, but If they are only doing noise is sthg to discuss as in any dist 
environment you will have timeouts and resource contraints. But at the moment 
jenkins is our official CI so any bugs there need ironing iiuc.

i.e CASSANDRA-17232 is sthg that comes up in jenkins a lot. On circle we only 
get it looping the test a1000 times and with difficulty.

> 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to