Changes between Version 14 and Version 15 of NewRunWebKitTests

Timestamp:

Feb 19, 2013 4:45:34 PM (11 years ago)

Author:

dpranke@chromium.org

Comment:

--

NewRunWebKitTests

@@ -84 +84 @@
 || || --no-show-results || don't display the summary HTML file in a web browser at the end of the run ||
 
-== More Advanced Scenarios ==
 
-=== Figuring out the command line passed to DumpRenderTree ===
-
-The command line used for DumpRenderTree is printed out if you pass the 'config' option to --print (along with a lot of other useful info):
-
-{{{
-% new-run-webkit-tests --print config,default -n --platform chromium-mac
-Using port 'chromium-mac-snowleopard'
-Test configuration: <snowleopard, x86, release, cpu>
-Placing test results in /Volumes/Src/src/dev/src/webkit/Release/layout-test-results
-Using Release build
-Pixel tests enabled
-Regular timeout: 6000, slow test timeout: 30000
-Command line: /Volumes/Src/src/dev/src/xcodebuild/Release/DumpRenderTree.app/Contents/MacOS/DumpRenderTree --test-shell --pixel-tests=/Volumes/Src/src/dev/src/webkit/Release/layout-test-results/png_result0.png
-Worker model: processes
-
-Running 16 DumpRenderTrees in parallel over 345 shards (1 locked)
-
-8561 tests ran as expected (16450 didn't run).
-%
-}}}
-
-===  A recommended set of command-line flags ===
+==  A recommended set of command-line flags ==
 
 dpranke@chromium.org has spent a lot of time hacking on NRWT. The command line argument he most frequently uses are: 
 
 {{{
-% new-run-webkit-tests --clobber-results --no-new-test-results --no-show-results --no-retry-failures --print config,default 
+% new-run-webkit-tests --clobber-results --no-new-test-results --no-show-results --no-retry-failures
 }}}
 
-=== Generating rebaselines into a specific platform path ===
+== Generating rebaselines into a specific platform path ==
 
 It may be desired to generate results using a given platform and expect it to be the same in some variations of that same platform, like in Qt which have qt-5.0-wk1, qt-5.0-wk2, and so many other options. The following line would run tests using Qt5 and WK2 but instead of placing the results onto that specific folder, it'll place the results into qt-5.0-wk1 folder: