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

Issue 759753010: Fix date_time_test to not assume a particular slowness of running code. (Closed)

Created:
6 years ago by Lasse Reichstein Nielsen
Modified:
6 years ago
Reviewers:
ricow1
CC:
reviews_dartlang.org
Visibility:
Public.

Description

Fix date_time_test to not assume a particular slowness of running code. R=ricow@google.com Committed: https://code.google.com/p/dart/source/detail?r=42083

Patch Set 1 #

Total comments: 2

Patch Set 2 : Add print every 1M loops if there is no progress. #

Unified diffs Side-by-side diffs Delta from patch set Stats (+8 lines, -6 lines) Patch
M tests/corelib/date_time_test.dart View 1 1 chunk +8 lines, -6 lines 0 comments Download

Messages

Total messages: 6 (1 generated)
Lasse Reichstein Nielsen
Remove the counter, and just run until Date.now() returns a time with a different millisecond ...
6 years ago (2014-12-03 06:51:07 UTC) #2
ricow1
lgtm, suggestion for making this easier to debug in case we see a timeout on ...
6 years ago (2014-12-03 06:55:46 UTC) #3
Lasse Reichstein Nielsen
https://codereview.chromium.org/759753010/diff/1/tests/corelib/date_time_test.dart File tests/corelib/date_time_test.dart (right): https://codereview.chromium.org/759753010/diff/1/tests/corelib/date_time_test.dart#newcode17 tests/corelib/date_time_test.dart:17: var t2 = new DateTime.now(); On 2014/12/03 06:55:46, ricow1 ...
6 years ago (2014-12-03 07:14:48 UTC) #4
ricow1
lgtm
6 years ago (2014-12-03 07:17:10 UTC) #5
Lasse Reichstein Nielsen
6 years ago (2014-12-03 07:21:06 UTC) #6
Message was sent while issue was closed.
Committed patchset #2 (id:20001) manually as 42083 (presubmit successful).

Powered by Google App Engine
This is Rietveld 408576698