[SCM] WebKit Debian packaging branch, debian/experimental, updated. upstream/1.3.3-9427-gc2be6fc

Wed Dec 22 12:34:33 UTC 2010

The following commit has been merged in the debian/experimental branch:
commit e3210941d0e95ba9927e7b3438550934340c0f31
Author: tony at chromium.org <tony at chromium.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Date:   Wed Aug 25 17:10:11 2010 +0000

    2010-08-25  Tony Chang  <tony at chromium.org>
    
            Reviewed by Ojan Vafai.
    
            [chromium] remove chromium.Interval layout test
            https://bugs.webkit.org/show_bug.cgi?id=44614
    
            chromium.Interval is moving into the benchmarking namespace
            and not being exposed by default.
    
            * platform/chromium/fast/dom/interval-expected.txt: Removed.
            * platform/chromium/fast/dom/interval.html: Removed.
    
    git-svn-id: http://svn.webkit.org/repository/webkit/trunk@66020 268f45cc-cd09-0410-ab3c-d52691b4dbfc

diff --git a/LayoutTests/ChangeLog b/LayoutTests/ChangeLog
index a9dbc95..3fcbab2 100644
--- a/LayoutTests/ChangeLog
+++ b/LayoutTests/ChangeLog
@@ -1,3 +1,16 @@
+2010-08-25  Tony Chang  <tony at chromium.org>
+
+        Reviewed by Ojan Vafai.
+
+        [chromium] remove chromium.Interval layout test
+        https://bugs.webkit.org/show_bug.cgi?id=44614
+
+        chromium.Interval is moving into the benchmarking namespace
+        and not being exposed by default.
+
+        * platform/chromium/fast/dom/interval-expected.txt: Removed.
+        * platform/chromium/fast/dom/interval.html: Removed.
+
 2010-08-25  Pavel Podivilov  <podivilov at chromium.org>
 
         Reviewed by Pavel Feldman.
diff --git a/LayoutTests/platform/chromium/fast/dom/interval-expected.txt b/LayoutTests/platform/chromium/fast/dom/interval-expected.txt
deleted file mode 100644
index f69fc7f..0000000
--- a/LayoutTests/platform/chromium/fast/dom/interval-expected.txt
+++ /dev/null
@@ -1,9 +0,0 @@
-This tests that the chromium.Interval functionality works correctly.
-
-PASS - initial zero
-PASS - start
-PASS - restart
-PASS - initial stop
-PASS - stop
-PASS - stopped
-PASS - re-stopped
diff --git a/LayoutTests/platform/chromium/fast/dom/interval.html b/LayoutTests/platform/chromium/fast/dom/interval.html
deleted file mode 100644
index 23d923b..0000000
--- a/LayoutTests/platform/chromium/fast/dom/interval.html
+++ /dev/null
@@ -1,77 +0,0 @@
-<html>
-<body onload="test()">
-<div id="result">
-<p>
-This tests that the chromium.Interval functionality works correctly.
-</p>
-</div>
-<script>
-if (window.layoutTestController) {
-  layoutTestController.dumpAsText();
-}
-
-var resultDiv = document.getElementById("result");
-
-function check(name, passed, debug_output) {
-  if (passed) {
-    resultDiv.innerHTML += "PASS - " + name + "<br>";
-  } else {
-    resultDiv.innerHTML += "FAIL - " + name + ", debug_output: " + debug_output + "<br>";
-  }
-}
-
-// Spin loop for a short time
-function pause(millisecs) {
-  var start = new Date();
-  while ((new Date() - start) < millisecs);
-}
-
-
-function test() {
-  var interval = new chromium.Interval();
-
-  // Verify initialization.
-  var ms = interval.microseconds();
-  check("initial zero", ms == 0, "[ms: " + ms + "]");
-
-  // Verify that starting the timer works.
-  interval.start();
-  pause(50);
-  ms = interval.microseconds();
-  // Due to clock skew and granularity, we see sporadic failures if we check for
-  // ms >= 50000, so add a bit of buffer.
-  check("start", ms >= 49000, "[ms: " + ms + "]");
-
-  // Verify that restarting the interval should reset the beginning time
-  interval.start();
-  pause(1);
-  ms = interval.microseconds();
-  check("restart", ms > 0 && ms < 50000, "[ms: " + ms + "]");
-
-  // Verify that calling stop() before start() has no effect.
-  var interval = new chromium.Interval();
-  interval.stop();
-  ms = interval.microseconds();
-  check("initial stop", ms == 0, "[ms: " + ms + "]");
-
-  // Verify a start/stop sequence.
-  interval.start();
-  pause(50);
-  interval.stop();
-  ms = interval.microseconds();
-  // On debug bots we've seen times as high as 250000.
-  check("stop", ms > 0 && ms < 300000, "[ms: " + ms + "]");
-
-  // Verify that the timer is really stopped.
-  var ms2 = interval.microseconds();
-  check("stopped", ms == ms2, "[ms: " + ms + "]" + "[ms2: " + ms2 + "]");
-
-  // Verify that re-stopping the timer works.
-  pause(50);
-  interval.stop();
-  ms2 = interval.microseconds();
-  check("re-stopped", ms2 > ms, "[ms: " + ms + "]" + "[ms2: " + ms2 + "]");
-}
-</script>
-</body>
-</html>

-- 
WebKit Debian packaging

