If you don't ever run new-run-webkit-tests, you can stop reading. If you do, then it might interest you to know that by popular demand (okay, two people), I have added a line that prints the actual command line used to invoke DumpRenderTree as part of the config output, e.g.:
$ new-run-webkit-tests -n --print config,default --platform chromium-mac fast/html/keygen.html Defaulting to one child - see https://bugs.webkit.org/show_bug.cgi?id=38553 Using port 'chromium-mac' Placing test results in /Volumes/Src/src/c.wdev/src/webkit/Release/layout-test-results Using Release build Pixel tests enabled Regular timeout: 6000, slow test timeout: 30000 Running one TestShell Command line: /Volumes/Src/src/c.wdev/src/xcodebuild/Release/TestShell.app/Contents/MacOS/TestShell --pixel-tests=/Volumes/Src/src/c.wdev/src/webkit/Release/layout-test-results/png_result0.png --layout-tests Worker model: threads $ I have also added the '-n' / '--dry-run' flag, which does everything new-run-webkit-tests normally does except actually run the tests. You can use this to quickly check the configuration info as above, or to sanity check that your build is okay, your test_expectations are okay, etc. I hope this is helpful, -- Dirk _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
