summaryrefslogtreecommitdiffstats
path: root/webkit/tools/layout_tests/run_webkit_tests.py
Commit message (Expand)AuthorAgeFilesLines
* Get rid of the concept of shardable directories. Just shard everythingojan@chromium.org2010-01-121-11/+5
* Remove remaining layout tests under src/webkit/data/layout_tests. Alldpranke@google.com2009-12-231-9/+5
* Fix some expectations for tests in the chrome and pending directories:dpranke@google.com2009-12-171-2/+2
* Modify run_webkit_tests to run in a single thread when num-test-shells==1.dpranke@google.com2009-12-161-8/+19
* Shard the editing tests. Now that the http tests have movedojan@chromium.org2009-12-161-1/+1
* By popular (?) demand, add some more options for different styles of output.dpranke@google.com2009-12-151-41/+102
* Fix bug 30408, 30380dpranke@google.com2009-12-151-1/+1
* Shard the loader directory. Should eek out ~20-40 more seconds on ojan@chromium.org2009-12-151-2/+3
* Shard the http tests on linux as well. They seem to be justojan@chromium.org2009-12-141-3/+5
* Remove the 'score.txt' file that run_webkit_tests writes to the results dir.dpranke@google.com2009-12-131-6/+0
* Logging cleanup for run_webkit_tests. This significantly revises the outputdpranke@google.com2009-12-111-161/+264
* It turns out that turning on max-workers (likely) made http testsojan@chromium.org2009-12-101-2/+1
* Update run_webkit_tests to generate an 'unexpected_results.json' file in thedpranke@google.com2009-12-091-210/+190
* 1. Shard the http tests on the mac.ojan@chromium.org2009-12-091-14/+8
* Try running apache for linux layout tests. Hopefully this will reduce httpojan@chromium.org2009-12-081-1/+1
* Take three at enabling max-workers for Lighttpd. The UI bots don'tojan@chromium.org2009-12-081-1/+2
* Revert 33975 - Take two at enabling maxworkers for lighttpd. Use SIGKILL insteadcpu@chromium.org2009-12-071-2/+1
* Take two at enabling max-workers for lighttpd. Use SIGKILL insteadojan@chromium.org2009-12-071-1/+2
* Handle the case where there are no skipped files properly.dpranke@google.com2009-12-051-1/+1
* Modify run_webkit_tests to not retry crashes, and to always consider themdpranke@google.com2009-12-051-12/+25
* Actually, it looks like this causes flakiness on the Windowsojan@chromium.org2009-12-041-1/+1
* Shard the svg directories as well. This should buy another ~20 secondsojan@chromium.org2009-12-041-1/+1
* Revise run_webkit_test.PrepareListsAndPrintOutput() to keep accurate countsdpranke@google.com2009-12-041-22/+34
* Revert 33757 - Use multiple workers with lighttpd. Hopefully this will reducevandebo@google.com2009-12-041-2/+1
* Use multiple workers with lighttpd. Hopefully this will reduceojan@chromium.org2009-12-041-1/+2
* Actually, this looks to be pretty stable on the V8-latest builders.ojan@chromium.org2009-12-031-8/+2
* Un-revert r33715 (i.e., re-apply r33709 and r33640), we think the failures weredpranke@google.com2009-12-031-274/+376
* Rollback r33709, r33640 until we can figure out why the output is gettingdpranke@google.com2009-12-031-376/+274
* Shard the fast and http directories on the V8-latest webkit bots.ojan@chromium.org2009-12-031-1/+10
* Modify run_webkit_tests to process results incrementally as they happen, insteaddpranke@google.com2009-12-031-22/+18
* Clean up the statistics reported by run_webkit_tests to be easier to follow.dpranke@google.com2009-12-031-269/+375
* Use Apache for all Mac builders. The Mac V8-latest builder has beenojan@chromium.org2009-11-301-2/+1
* Use apache on the Mac on V8-Latest builders as an experimentojan@chromium.org2009-11-251-1/+14
* Move the starting of the websocket server next to the starting of the ojan@chromium.org2009-11-251-5/+5
* Only retry unexpected failures once. Really the retry functionalityojan@chromium.org2009-11-201-1/+1
* Retry failing tests. Keeps the original list of failing tests forojan@chromium.org2009-11-191-70/+116
* Fix websocket tests to run.ukai@chromium.org2009-11-161-4/+5
* Clobber layout test results at the beginning of each run.ojan@chromium.org2009-11-021-0/+12
* Rename a variable to avoid shadowing.dpranke@google.com2009-10-291-3/+3
* Start/stop Web Socket Secure server if necessary.yuzo@chromium.org2009-10-161-1/+6
* Change run_webkit_tests.py to start up/shut down pywebsocket server if needed.yuzo@chromium.org2009-10-141-0/+18
* 1. Removing doubbling the timeout for tests that run in parallel.ojan@chromium.org2009-10-131-9/+9
* Fix rebaseline tool that I just broke by testing properly for ojan@chromium.org2009-10-081-1/+2
* Stop computing simplified diffs. For now, leave the oldojan@chromium.org2009-10-081-2/+0
* Fix --new-baseline to honor the --platform flag. dpranke@google.com2009-10-071-1/+1
* Distinguish between different types of failures in the JSONojan@chromium.org2009-10-061-0/+4
* Tweak the layout_test driver scripts to shard the tests completely and thendpranke@google.com2009-09-301-9/+39
* Re-submit CL 27576 w/ fixdpranke@google.com2009-09-301-77/+25
* Revert 27576dpranke@google.com2009-09-301-24/+77
* Refactor run_webkit_tests a bit so we can extract the list of test filesdpranke@google.com2009-09-301-77/+24