|
|
Created:
5 years ago by v8-autoroll Modified:
5 years ago CC:
chromium-reviews Base URL:
https://chromium.googlesource.com/chromium/src.git@master Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionUpdate V8 to version 4.9.136.
Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/d93a58ce..3af92e97
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.
TBR=hablich@chromium.org,machenbach@chromium.org,yangguo@chromium.org,vogelheim@chromium.org
Patch Set 1 #Messages
Total messages: 19 (8 generated)
The CQ bit was checked by v8-autoroll@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1497763004/1 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1497763004/1
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: mac_chromium_rel_ng on tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)
On 2015/12/04 09:48:06, commit-bot: I haz the power wrote: > Try jobs failed on following builders: > mac_chromium_rel_ng on tryserver.chromium.mac (JOB_FAILED, > http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...) Looks like a real thing although I have no clue how this test is set-up. If it fails a second time this needs to be investigated.
The CQ bit was checked by v8-autoroll@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1497763004/1 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1497763004/1
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: linux_chromium_chromeos_ozone_rel_ng on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by v8-autoroll@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1497763004/1 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1497763004/1
The CQ bit was unchecked by hablich@chromium.org
Looks legit to me. Stopping auto-roller and starting bi-sect.
Maybe yang knows. There's a check in builtins firing...
machenbach@chromium.org changed reviewers: + bmeurer@chromium.org
+ bmeurer: The failure on asan is about arraybuffer: https://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_asa...
Description was changed from ========== Update V8 to version 4.9.136. Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/d93a58ce..3af92e97 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. TBR=hablich@chromium.org,machenbach@chromium.org,yangguo@chromium.org,vogelhe... ========== to ========== Update V8 to version 4.9.136. Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/d93a58ce..3af92e97 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. TBR=hablich@chromium.org,machenbach@chromium.org,yangguo@chromium.org,vogelhe... ==========
Message was sent while issue was closed.
On 2015/12/04 10:33:35, Michael Achenbach (slow) wrote: > + bmeurer: > > The failure on asan is about arraybuffer: > https://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_asa... Clusterfuzz also agrees: https://code.google.com/p/chromium/issues/detail?id=565917 |