Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(1049)

Issue 48493002: Increase the 20 second timeout value of the unittest framework higher (Closed)

Created:
7 years, 1 month ago by kustermann
Modified:
7 years, 1 month ago
Reviewers:
ricow1, kasperl
CC:
reviews_dartlang.org, gram, blois
Visibility:
Public.

Description

Increase the 20 second timeout value of the unittest framework higher Tests going over the 20 seconds is causing us random failures on the buildbots. Until we have a custom unittest configuration for our testing scripts, we'll increase the default timeout to 2 minutes. R=ricow@google.com Committed: https://code.google.com/p/dart/source/detail?r=29349

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+2 lines, -2 lines) Patch
M pkg/unittest/lib/src/configuration.dart View 1 chunk +1 line, -1 line 0 comments Download
M pkg/unittest/lib/src/simple_configuration.dart View 1 chunk +1 line, -1 line 0 comments Download

Messages

Total messages: 7 (0 generated)
kustermann
7 years, 1 month ago (2013-10-28 10:32:36 UTC) #1
ricow1
LGTM
7 years, 1 month ago (2013-10-28 10:34:17 UTC) #2
kustermann
Committed patchset #1 manually as r29349 (presubmit successful).
7 years, 1 month ago (2013-10-28 10:36:54 UTC) #3
kustermann
@iposva/blois: I increased it now to two minutes -- so we shouldn't need any "opting ...
7 years, 1 month ago (2013-10-28 10:38:59 UTC) #4
kasperl
LGTM as a short-term fix.
7 years, 1 month ago (2013-10-28 11:17:33 UTC) #5
Ivan Posva
On 2013/10/28 10:38:59, kustermann wrote: > @iposva/blois: I increased it now to two minutes -- ...
7 years, 1 month ago (2013-10-28 18:36:01 UTC) #6
Ivan Posva
7 years, 1 month ago (2013-10-28 18:37:47 UTC) #7
Message was sent while issue was closed.
On 2013/10/28 18:36:01, Ivan Posva wrote:
> On 2013/10/28 10:38:59, kustermann wrote:
> > @iposva/blois: I increased it now to two minutes -- so we shouldn't need any
> > "opting out tests".
> > 
> > This is not mid/long term solution.
> > 
> > We should still figure out why the tests are suddently taking more time to
> > execute -- maybe performance regressions ...?
> 
> The problem with the unit test framework is that we do not report the times of
> the individual test runs, so it is not clear whether these tests were at 19.8
> seconds and now just by some little fluctuation we are over the threshold or
> whether we at least doubled the runtime. We should probably print out a
message
> if a test finishes within 10% or 20% of the allowable timeout.
> 
> -Ivan

Filed https://code.google.com/p/dart/issues/detail?id=14531

-Ivan

Powered by Google App Engine
This is Rietveld 408576698