Changes between Version 13 and Version 14 of Rebaseline
- Timestamp:
- Sep 12, 2011 10:44:36 AM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Rebaseline
v13 v14 3 3 The rebaselining tool automatically produces new expected results using the layout test results from buildbots. The goal is that after running this tool, the working copy will be ready to create a change containing all new baselines. 4 4 5 The tool is written in Python and lives in `Tools/Scripts` ([http://trac.webkit.org/browser/trunk/Tools/Scripts/rebaseline-chromium-webkit-tests]).5 The tool is part of the webkit-patch suite of utilities 6 6 7 7 == How does this tool work? == … … 18 18 * Make sure the test files exist in repository and the build bots have cycled at least once after they were committed. If you are not sure, check the Release version of [http://build.chromium.org/buildbot/layout_test_results/ buildbot layout archive] to see whether your test results are available. By default, the rebaselining tool retrieves new baselines from the release version of buildbot layout test archive. 19 19 * Update `test_expectations.txt`: add flag `REBASELINE` to the tests that need to be rebaselined. 20 * Run rebaselining script: `Tools/Scripts/ rebaseline-chromium-webkit-tests`20 * Run rebaselining script: `Tools/Scripts/webkit-patch rebaseline-expectations` 21 21 * If the script runs successfully, new baselines (expected files) are added to SVN repository and the rebaselined tests are removed from `test_expectations.txt`. 22 22 * The tool launches a html page to compare the old and new baselines. Check the new baseline changes are expected.