lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dawid Weiss (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-4301) re-enable test timeout, but factor in nightly, multiplier, clover
Date Mon, 13 Aug 2012 07:23:38 GMT

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

Dawid Weiss commented on LUCENE-4301:
-------------------------------------

Let's take the maximum we know of and re-enable. Timeouts are meant to end hung tests that
nobody looks at (jenkins). Even two hours per suite is fine as long as it is terminated at
some point.
                
> re-enable test timeout, but factor in nightly, multiplier, clover
> -----------------------------------------------------------------
>
>                 Key: LUCENE-4301
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4301
>             Project: Lucene - Core
>          Issue Type: Task
>          Components: general/test
>            Reporter: Robert Muir
>
> Having a test timeout is great (for things like test hangs), but its going to cause a
lot of failed builds until we factor in the various flags that can cause tests to run longer,
or enable longer-running tests.
> Its hard to say what the limits should be since jenkins history is pretty limited at
the moment (only 2 nightly runs history available)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message