All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=887483

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=cad72fd7ac55f84df35e1dd671f0e4469e2ae6213ccd600d344270877f2ad45c


Bot(s) for this bug's original alert(s):

Android Nexus5 Perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/15a4441f640000

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/15a4441f640000

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/103e54a4e40000

📍 Found significant differences after each of 3 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/103e54a4e40000

Reland "Enable Perfetto by default for all telemetry tests" by oysteine@google.com
https://chromium.googlesource.com/chromium/src/+/0f374eff414ec0683aafbe2aae3fd405a4fcc221
26.44 → 28.52 (+2.082)

Turn on full masking with untrusted-code-mitigations by jarin@chromium.org
https://chromium.googlesource.com/v8/v8/+/6a6f050e18b90d5b498d85455e598ca68b14238f
28.67 → 32.14 (+3.467)

Revert "Reland "Enable Perfetto by default for all telemetry tests"" by pasko@chromium.org
https://chromium.googlesource.com/chromium/src/+/f36de8b1bdc40bf31455b052ef63338072b093da
32.17 → 30.35 (-1.824)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

The Perfetto-related regression is somewhat expected, see:  crbug.com/888558 , and it is paired with the improvement from the revert.

The other regression attributed to "Turn on full masking with untrusted-code-mitigations by jarin@chromium.org" needs more investigation.