From 758e8cf69b071869e53cf50c350e35ab3b6fbc2d Mon Sep 17 00:00:00 2001 From: "thomasvl@chromium.org" Date: Wed, 19 Aug 2009 21:28:38 +0000 Subject: Some quick notes about the mac reference builds for anyone that might need to update them in the future. Review URL: http://codereview.chromium.org/174070 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@23748 0039d316-1c4b-4281-b951-d872f2087c98 --- chrome/tools/test/reference_build/chrome_mac/notes.txt | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 chrome/tools/test/reference_build/chrome_mac/notes.txt (limited to 'chrome/tools') diff --git a/chrome/tools/test/reference_build/chrome_mac/notes.txt b/chrome/tools/test/reference_build/chrome_mac/notes.txt new file mode 100644 index 0000000..7ba4770 --- /dev/null +++ b/chrome/tools/test/reference_build/chrome_mac/notes.txt @@ -0,0 +1,10 @@ +You want to be very careful about updating the reference builds, because it +means changing the baseline all new builds are compared to on the performance +graphs and can easily let regressions slip in. + +The Chromium and Google Chrome builds the same revisions so you can compare +Google Chrome and Chromium performance data. + +For the Google Chrome build, you need to disable Keystone within the build so +the bots won't have it updated to more recent builds (just remove the framework +and nuke the plist keys). -- cgit v1.1