lucene-dev mailing list archives

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


Dawid Weiss commented on LUCENE-4301:

I should probably add that there is no way to calculate the timeout value from the code because
the decisions take place before the test code is started. It could be a system property override
but then you'd have to set it properly based on your jenkins configuration, etc.

I'll re-enable for max. suite time = 2 hours? Alternatively override @TimeoutSuite on a particular
test class that you know lasts longer than that.
> re-enable test timeout, but factor in nightly, multiplier, clover
> -----------------------------------------------------------------
>                 Key: LUCENE-4301
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message