From fa2ff742edce01bdeaa1abca833bd738cc830a75 Mon Sep 17 00:00:00 2001 From: "fschneider@chromium.org" Date: Mon, 29 Aug 2011 08:46:35 +0000 Subject: [PATCH] Adjust unit test to avoid flakyness when running with the ARM simulator. In some cases the assert that the test function is not optimized fails because the function may be optimized already after the second invocation. (e.g. when running slow in debug mode) Review URL: http://codereview.chromium.org/7778009 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9034 ce2b1a6d-e550-0410-aec6-3dcde31c8c00 --- test/mjsunit/assert-opt-and-deopt.js | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/test/mjsunit/assert-opt-and-deopt.js b/test/mjsunit/assert-opt-and-deopt.js index f589868..c9adb5b 100644 --- a/test/mjsunit/assert-opt-and-deopt.js +++ b/test/mjsunit/assert-opt-and-deopt.js @@ -54,7 +54,7 @@ OptTracker.OptimizationState = { * that you later want to track de/optimizations for. It is necessary because * tests are sometimes executed several times in a row, and you want to * disregard counts from previous runs. - */ + */ OptTracker.prototype.CheckpointOptCount = function(func) { this.opt_counts_[func] = %GetOptimizationCount(func); }; @@ -148,7 +148,7 @@ tracker.AssertIsOptimized(f, false); tracker.AssertDeoptHappened(f, false); tracker.AssertDeoptCount(f, 0); -for (var i = 0; i < 2; i++) f(1); +f(1); tracker.AssertOptCount(f, 0); tracker.AssertIsOptimized(f, false); -- 2.7.4