summaryrefslogtreecommitdiffstats
path: root/webkit/tools/layout_tests/run_webkit_tests.py
diff options
context:
space:
mode:
authorojan@chromium.org <ojan@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-12-04 02:23:58 +0000
committerojan@chromium.org <ojan@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-12-04 02:23:58 +0000
commit8024f418637a122df0c05c71cfe76bfc25c32d18 (patch)
tree311986a5b40274f5eddc9c0aedb43d17a637a996 /webkit/tools/layout_tests/run_webkit_tests.py
parentbd570d0d7e1bc9d1488b06d5810e9c03fcdffce0 (diff)
downloadchromium_src-8024f418637a122df0c05c71cfe76bfc25c32d18.zip
chromium_src-8024f418637a122df0c05c71cfe76bfc25c32d18.tar.gz
chromium_src-8024f418637a122df0c05c71cfe76bfc25c32d18.tar.bz2
Actually, it looks like this causes flakiness on the Windows
debug bots. The V8-Latest bots are release only. :( Once we get a better handle on http flakiness on Windows, we can try to shard the http tests again. Or, we could just shard them on linux/mac. For now, I'm just reverting to avoid leaving the tree in a bad state. Review URL: http://codereview.chromium.org/460064 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@33779 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'webkit/tools/layout_tests/run_webkit_tests.py')
-rwxr-xr-xwebkit/tools/layout_tests/run_webkit_tests.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/webkit/tools/layout_tests/run_webkit_tests.py b/webkit/tools/layout_tests/run_webkit_tests.py
index fdac3ae..bd1a239 100755
--- a/webkit/tools/layout_tests/run_webkit_tests.py
+++ b/webkit/tools/layout_tests/run_webkit_tests.py
@@ -136,7 +136,7 @@ class TestRunner:
self._http_server = http_server.Lighttpd(options.results_directory)
self._shardable_directories = ['chrome', 'LayoutTests', 'pending', 'fast',
- 'http', 'tests', 'svg']
+ 'svg']
self._websocket_server = websocket_server.PyWebSocket(
options.results_directory)