Index: tools/webrtc_perf_expectations/README |
diff --git a/tools/webrtc_perf_expectations/README b/tools/webrtc_perf_expectations/README |
new file mode 100644 |
index 0000000000000000000000000000000000000000..972aceb6b6478ddfb22a1a01b60fcc9510e26695 |
--- /dev/null |
+++ b/tools/webrtc_perf_expectations/README |
@@ -0,0 +1,13 @@ |
+======== |
+Overview |
no longer working on chromium
2013/04/08 14:33:26
should we follow some existing README pattern, lik
|
+======== |
+ |
+See http://dev.chromium.org/developers/tree-sheriffs/perf-sheriffs#TOC-Selecting-an-acceptable-range-of-results |
+for a general explanation of how performance expectations work. |
+ |
+Instead of the regular make_expectations.py call, run this: |
+ |
+../perf_expectations/make_expectations.py -c webrtc_perf_expectations.cfg |
+ |
+We keep the WebRTC perf expectations aside since the tests are running on an |
+internal master for now. |