Changeset 130317 in webkit

Timestamp:

Oct 3, 2012, 1:17:48 PM (13 years ago)

Author:

ojan@chromium.org

Message:

Fix some style violations in perparation for changing this code.

• resources/magnitude-perf.js:

(Magnitude.run):
(Magnitude._logIterationInfo):
(Magnitude._runIteration):

Location:

trunk/LayoutTests

Files:

• ChangeLog (modified) (1 diff)
• resources/magnitude-perf.js (modified) (3 diffs)

trunk/LayoutTests/ChangeLog

@@ +1 @@
+2012-10-03  Ojan Vafai  <ojan@chromium.org>
+
+        Fix some style violations in perparation for changing this code.
+        * resources/magnitude-perf.js:
+        (Magnitude.run):
+        (Magnitude._logIterationInfo):
+        (Magnitude._runIteration):
+
 2012-10-03  Dirk Pranke  <dpranke@chromium.org>
 

trunk/LayoutTests/resources/magnitude-perf.js

@@ -53 +53 @@
 
     Magnitude._magnitudes = [];
-    for (var i = 0; i < Magnitude._numPoints; i++) {
+    for (var i = 0; i < Magnitude._numPoints; i++)
         Magnitude._magnitudes.push(Math.pow(2, i));
-    }
 
     var milliseconds = 50;
@@ -163 +162 @@
         iterationsArray.push(iterations);
         Magnitude._debug("magnitude: " + magnitude + " iterations: " + iterations + " runsPerIteration " + runsPerIteration +
-                " loop-time " + milliseconds + " time/iteration(ms): " + milliseconds / iterations);
+            " loop-time " + milliseconds + " time/iteration(ms): " + milliseconds / iterations);
     }
 
@@ -222 +221 @@
     var iterations = 0;
     if (window.chromium) {
-      // FIXME: If using microseconds turns out to be less flaky, expose microseconds
-      // from JSC or testRunner and use them. Otherwise, get rid of this block.
-      var microseconds = milliseconds * 1000;
-      var interval = new chromium.Interval();
-      interval.start();
-      while (interval.microseconds() < microseconds) {
-          // Loop runsPerIteration times to reduce errors due to the overhead and granularity of the Date object.
-          for (var i = 0; i < runsPerIteration; i++) {
-              test(magnitude);
-          }
-          iterations++;
-      }
-      interval.stop();
+        // FIXME: If using microseconds turns out to be less flaky, expose microseconds
+        // from JSC or testRunner and use them. Otherwise, get rid of this block.
+        var microseconds = milliseconds * 1000;
+        var interval = new chromium.Interval();
+        interval.start();
+        while (interval.microseconds() < microseconds) {
+            // Loop runsPerIteration times to reduce errors due to the overhead and granularity of the Date object.
+            for (var i = 0; i < runsPerIteration; i++)
+                test(magnitude);
+            iterations++;
+        }
+        interval.stop();
     } else {
-      var start = Date.now();
-      while (Date.now() - start < milliseconds) {
-          // Loop runsPerIteration times to reduce errors due to the overhead and granularity of the Date object.
-          for (var i = 0; i < runsPerIteration; i++) {
-              test(magnitude);
-          }
-          iterations++;
-      }
+        var start = Date.now();
+        while (Date.now() - start < milliseconds) {
+            // Loop runsPerIteration times to reduce errors due to the overhead and granularity of the Date object.
+            for (var i = 0; i < runsPerIteration; i++)
+                test(magnitude);
+            iterations++;
+        }
     }
     return iterations;