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

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


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

mac

Assigning to v8-autoroll@chromium.org because this is the only CL in range:
Update V8 to version 6.7.103.

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/6887bb98..8c5929de

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;luci.chromium.try:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,machenbach@chromium.org,kozyatinskiy@chromium.org,sergiyb@chromium.org

Change-Id: Id1149be5925c8733c6cf4be6ad75bee0ca955827
Reviewed-on: https://chromium-review.googlesource.com/967953
Reviewed-by: v8 autoroll <v8-autoroll@chromium.org>
Commit-Queue: v8 autoroll <v8-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#544005}

Looks like the v8 roll above increased Mac binary size by 276KiB. Can someone from v8 team take a look?

Maybe https://chromium.googlesource.com/v8/v8/+/fd70917d520ea7bbcc5e401776c7dac7120c6942 ?

Statuses on crbug seem broken: the duped bug is  https://crbug.com/822287 .