BASELINE: Update Chromium to 70.0.3538.78

Change-Id: Ie634710bf039e26c1957f4ae45e101bd4c434ae7
Reviewed-by: Michael Brüning <michael.bruning@qt.io>

4 files changed, 22 insertions, 47 deletions

diff --git a/chromium/docs/speed/benchmark/benchmark_ownership.md b/chromium/docs/speed/benchmark/benchmark_ownership.md
index b6a1892bcca..5297041eb4e 100644
--- a/chromium/docs/speed/benchmark/benchmark_ownership.md
+++ b/chromium/docs/speed/benchmark/benchmark_ownership.md
@@ -29,12 +29,12 @@ There can be multiple owners of a benchmark, for example if there are multiple t
   which will be automatically added to the bug by the perf dashboard; and a link
   to documentation (which will be added to regression bugs in Q3 2018).
 
-1. Run `tools/perf/generate_perf_data` to update `tools/perf/benchmarks.csv`.
-1. Upload the benchmark python file and `benchmarks.csv` to a CL for review. Please add any previous owners to the review.
+1. Run `tools/perf/generate_perf_data` to update `tools/perf/benchmark.csv`.
+1. Upload the benchmark python file and `benchmark.csv` to a CL for review. Please add any previous owners to the review.
 
 ### C++ Perf Benchmarks
 1. Open [`src/tools/perf/core/perf_data_generator.py`](https://cs.chromium.org/chromium/src/tools/perf/core/perf_data_generator.py).
 1. Find the BenchmarkMetadata for the benchmark. It will be in a dictionary named `NON_TELEMETRY_BENCHMARKS` or `NON_WATERFALL_BENCHMARKS`.
 1. Update the email (first field of `BenchmarkMetadata`).
-1. Run `tools/perf/generate_perf_data` to update `tools/perf/benchmarks.csv`.
-1. Upload `perf_data_generator.py` and `benchmarks.csv` to a CL for review. Please add any previous owners to the review.
+1. Run `tools/perf/generate_perf_data` to update `tools/perf/benchmark.csv`.
+1. Upload `perf_data_generator.py` and `benchmark.csv` to a CL for review. Please add any previous owners to the review.
diff --git a/chromium/docs/speed/diagnostic_metrics.md b/chromium/docs/speed/diagnostic_metrics.md
index 47d30430cdd..f1d9d135175 100644
--- a/chromium/docs/speed/diagnostic_metrics.md
+++ b/chromium/docs/speed/diagnostic_metrics.md
@@ -59,8 +59,6 @@ In the same way that when constructing a Summation Diagnostic we account for eve
 
 Some diagnostic metrics correlate with the higher level metric, but aren’t related in any precise way. For example, the top level FMP metric measures wall clock time. We could add a CPU time equivalent as a diagnostic metric, which is likely to have lower noise. In cases like this, we expect there to exist some monotonic function which approximately maps from the top level metric to the diagnostic metric, but this relationship could be quite rough.
 
-Slicing diagnostics are implemented in telemetry via [Related Histogram Maps](https://cs.chromium.org/chromium/src/third_party/catapult/tracing/tracing/value/diagnostics/related_histogram_map.html?q=RelatedHistogramMap&sq=package:chromium&l=16).
-
 ## Composing Diagnostics
 
 Many metrics will have multiple sets of diagnostics. For example, this set of FMP diagnostics involves Slicing, Summation, and Proxy Diagnostics.
diff --git a/chromium/docs/speed/perf_lab_platforms.md b/chromium/docs/speed/perf_lab_platforms.md
index 341d13dd6b6..68d437b2798 100644
--- a/chromium/docs/speed/perf_lab_platforms.md
+++ b/chromium/docs/speed/perf_lab_platforms.md
@@ -1,51 +1,29 @@
+
+[comment]: # (AUTOGENERATED FILE DO NOT EDIT)
+[comment]: # (See //tools/perf/generate_perf_data to make changes)
+
 # Platforms tested in the Performance Lab
 
 ## Android
 
- * [Nexus
-   5X](https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5X%20Perf)
-   (Chrome and Webview)
- * [Nexus
-   5](https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5%20Perf)
- * [Nexus
-   6](https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus6%20Perf) (Chrome and WebView)
- * [Nexus
-   7](https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus7v2%20Perf)
- * [Android
-   One](https://build.chromium.org/p/chromium.perf/builders/Android%20One%20Perf)
+ * [android-go-perf](https://ci.chromium.org/buildbot/chromium.perf/android-go-perf/): Android O.
+ * [Android Nexus5 Perf](https://ci.chromium.org/buildbot/chromium.perf/Android%20Nexus5%20Perf/): Android KOT49H.
+ * [android-nexus5x-perf](https://ci.chromium.org/buildbot/chromium.perf/android-nexus5x-perf/): Android MMB29Q.
+ * [Android Nexus5X WebView Perf](https://ci.chromium.org/buildbot/chromium.perf/Android%20Nexus5X%20WebView%20Perf/): Android AOSP MOB30K.
+ * [Android Nexus6 WebView Perf](https://ci.chromium.org/buildbot/chromium.perf/Android%20Nexus6%20WebView%20Perf/): Android AOSP MOB30K.
+
+## Linux
+
+ * [linux-perf](https://ci.chromium.org/buildbot/chromium.perf/linux-perf/): Ubuntu-14.04, 8 core, NVIDIA Quadro P400.
 
 ## Mac
 
- * [Mac
-   10.11](https://build.chromium.org/p/chromium.perf/builders/Mac%2010.11%20Perf)
- * [Mac
-   10.12](https://build.chromium.org/p/chromium.perf/builders/Mac%2010.12%20Perf)
- * [Retina
-   Mac](https://build.chromium.org/p/chromium.perf/builders/Mac%20Retina%20Perf)
- * [Macbook Pro
-   10.11](https://build.chromium.org/p/chromium.perf/builders/Mac%20Pro%2010.11%20Perf)
- * [Macbook Air
-   10.11](https://build.chromium.org/p/chromium.perf/builders/Mac%20Air%2010.11%20Perf)
- * [Mac Mini - 8GB running
-   10.12](https://build.chromium.org/p/chromium.perf/builders/Mac%20Mini%208GB%2010.12%20Perf)
+ * [mac-10_12_laptop_low_end-perf](https://ci.chromium.org/buildbot/chromium.perf/mac-10_12_laptop_low_end-perf/): MacBook Air, Core i5 1.8 GHz, 8GB RAM, 128GB SSD, HD Graphics.
+ * [mac-10_13_laptop_high_end-perf](https://ci.chromium.org/buildbot/chromium.perf/mac-10_13_laptop_high_end-perf/): MacBook Pro, Core i7 2.8 GHz, 16GB RAM, 256GB SSD, Radeon 55.
 
 ## Windows
 
- * [Zenbook](https://build.chromium.org/p/chromium.perf/builders/Win%20Zenbook%20Perf)
- * [Win 10 - High
-   DPI](https://build.chromium.org/p/chromium.perf/builders/Win%2010%20High-DPI%20Perf)
- * [Win 10](https://build.chromium.org/p/chromium.perf/builders/Win%2010%20Perf)
- * [Win 8](https://build.chromium.org/p/chromium.perf/builders/Win%208%20Perf)
- * [Win 7](https://build.chromium.org/p/chromium.perf/builders/Win%207%20Perf)
- * [Win 7 -
-   x64](https://build.chromium.org/p/chromium.perf/builders/Win%207%20x64%20Perf)
- * [Win 7 with ATI
-   GPU](https://build.chromium.org/p/chromium.perf/builders/Win%207%20ATI%20GPU%20Perf)
- * [Win 7 with Intel
-   GPU](https://build.chromium.org/p/chromium.perf/builders/Win%207%20Intel%20GPU%20Perf)
- * [Win 7 with nVidia
-   GPU](https://build.chromium.org/p/chromium.perf/builders/Win%207%20Nvidia%20GPU%20Perf)
-
-## Linux
+ * [win-10-perf](https://ci.chromium.org/buildbot/chromium.perf/win-10-perf/): Windows Intel HD 630 towers, Core i7-7700 3.6 GHz, 16GB RAM, Intel Kaby Lake HD Graphics 630.
+ * [Win 7 Nvidia GPU Perf](https://ci.chromium.org/buildbot/chromium.perf/Win%207%20Nvidia%20GPU%20Perf/): N/A.
+ * [Win 7 Perf](https://ci.chromium.org/buildbot/chromium.perf/Win%207%20Perf/): N/A.
 
- * [Ubuntu](https://build.chromium.org/p/chromium.perf/builders/Linux%20Perf)
diff --git a/chromium/docs/speed/perf_trybots.md b/chromium/docs/speed/perf_trybots.md
index dc8b5f4747a..5d92382cd22 100644
--- a/chromium/docs/speed/perf_trybots.md
+++ b/chromium/docs/speed/perf_trybots.md
@@ -14,7 +14,6 @@ patch applied.
   continuous integration suite.
 * The devices have the "maintenance mutex" enabled, reducing noise from
   background processes.
-* The devices are instrumented with BattOrs for power measurements.
 * Some regressions take multiple repeats to reproduce, and Pinpoint
   automatically runs multiple times and aggregates the results.
 * Some regressions reproduce on some devices but not others, and Pinpoint will