summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--chrome/tools/test/reference_build/chrome_mac/notes.txt10
1 files changed, 10 insertions, 0 deletions
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).