Commit 0cb2cd62 authored by v8-ci-autoroll-builder's avatar v8-ci-autoroll-builder Committed by Commit Bot

Update V8 to version 7.1.133.

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/604c50c8..aa61ad05

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;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com

Change-Id: If0586e0b77e61d7cbd22c2e23eed5587c03c0994
Reviewed-on: https://chromium-review.googlesource.com/1233182Reviewed-by: default avatarV8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#592367}
parent fab52382
...@@ -109,7 +109,7 @@ vars = { ...@@ -109,7 +109,7 @@ vars = {
# Three lines of non-changing comments so that # Three lines of non-changing comments so that
# the commit queue can handle CLs rolling V8 # the commit queue can handle CLs rolling V8
# and whatever else without interference from each other. # and whatever else without interference from each other.
'v8_revision': '604c50c84e672c099cbcbd6dd19928a0381d9688', 'v8_revision': 'aa61ad0595f22f36628561e59b34a87310d46e79',
# Three lines of non-changing comments so that # Three lines of non-changing comments so that
# the commit queue can handle CLs rolling swarming_client # the commit queue can handle CLs rolling swarming_client
# and whatever else without interference from each other. # and whatever else without interference from each other.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment