New issue
Advanced search Search tips

Issue 771803 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner: ----
Closed: Oct 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

buildbot failure in chromium on Win, revision f18dc4824eee4d272ea02011652d4c887f468300

Project Member Reported by nedngu...@google.com, Oct 4 2017

Issue description

Log: https://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Fchromium%2FWin%2F59604%2F%2B%2Frecipes%2Fsteps%2Fcompile%2F0%2Fstdout

Suspect due to v8 roll:
FAILED: gen/v8/snapshot.cc snapshot_blob.bin 
C:/b/depot_tools/win_tools-2_7_6_bin/python/bin/python.exe ../../v8/tools/run.py ./mksnapshot --startup_src gen/v8/snapshot.cc --random-seed 314159265 --startup_blob snapshot_blob.bin
==== C stack trace ===============================
	v8::internal::Heap::CreateInitialObjects [0x00743000+3792]
	v8::internal::SetupIsolateDelegate::SetupHeapInternal [0x007439D1+17]
	v8::internal::SetupIsolateDelegate::SetupHeap [0x006F1FB1+17]
	v8::internal::Isolate::Init [0x0053D734+9380]
	v8::SnapshotCreator::SnapshotCreator [0x002B89F5+245]
	v8::V8::CreateSnapshotDataBlob [0x002BACD1+33]
	main [0x002B1590+192]
	__scrt_common_main_seh [0x0081BD1A+248] (f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:283)
	BaseThreadInitThunk [0x76E7338A+18]
	RtlInitializeExceptionChain [0x77429A02+99]
	RtlInitializeExceptionChain [0x774299D5+54]
 
Components: Blink>JavaScript
Project Member

Comment 2 by bugdroid1@chromium.org, Oct 4 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/34f1811c8d3a3db366f2ae9c88eedf08fa1d7a97

commit 34f1811c8d3a3db366f2ae9c88eedf08fa1d7a97
Author: Ned Nguyen <nednguyen@google.com>
Date: Wed Oct 04 23:22:08 2017

Revert "Update V8 to version 6.3.257."

This reverts commit 95dd6223d1225dfeb444df6dcdeb16c29b7aaaa0.

Reason for revert: suspect causing compile failure
BUG:771803

Original change's description:
> Update V8 to version 6.3.257.
> 
> Summary of changes available at:
> https://chromium.googlesource.com/v8/v8/+log/22069a18..73d9476e
> 
> 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;master.tryserver.chromium.linux: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
> 
> Change-Id: Ibdfcc894e660d187b6ea53cd1f8e482415911d12
> Reviewed-on: https://chromium-review.googlesource.com/700721
> Reviewed-by: v8 autoroll <v8-autoroll@chromium.org>
> Commit-Queue: v8 autoroll <v8-autoroll@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#506538}

TBR=v8-autoroll@chromium.org,machenbach@chromium.org,hablich@chromium.org,kozyatinskiy@chromium.org

Change-Id: Idf91edeb3ff781fe302e2ca4ee72b1c800b87604
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux: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
Reviewed-on: https://chromium-review.googlesource.com/701408
Reviewed-by: Ned Nguyen <nednguyen@google.com>
Commit-Queue: Ned Nguyen <nednguyen@google.com>
Cr-Commit-Position: refs/heads/master@{#506556}
[modify] https://crrev.com/34f1811c8d3a3db366f2ae9c88eedf08fa1d7a97/DEPS

Not sure if you are on #chromium on IRC, but I mentioned  bug 743069 . I also see  bug 700525 .

https://build.chromium.org/p/chromium/builders/Win/builds/59604 is the failed build
https://build.chromium.org/p/chromium/builders/Win/builds/59605 is already in progress and does not contain your revert. If this build goes green, then likely the breakage was just a flake and the revert may have been unnecessary.
Labels: -Sheriff-Chromium
Status: Fixed (was: Untriaged)
(Chromium Sherrif) The bot is now working well -> Fixed.

Sign in to add a comment