Update V8 to version 3.27.8 (based on bleeding_edge revision r21370).

Update V8 to version 3.27.8 (based on bleeding_edge revision r21370).

Please reply to the V8 sheriff jkummerow@chromium.org in case of problems.

TBR=jkummerow@chromium.org
NOTREECHECKS=true

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=271630

[Jakob Kummerow, 2014-05-20 07:16:03]

lgtm

[commit-bot: I haz the power, 2014-05-20 07:16:10]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/machenbach@chromium.org/292953003/1

[Michael Achenbach, 2014-05-20 13:22:27]

The CQ bit was unchecked by machenbach@chromium.org

[Michael Achenbach, 2014-05-20 13:22:29]

The CQ bit was checked by machenbach@chromium.org

[commit-bot: I haz the power, 2014-05-20 13:23:34]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/machenbach@chromium.org/292953003/1

[commit-bot: I haz the power, 2014-05-20 13:25:14]

Change committed as 271630

[Alexei Svitkine (slow), 2014-05-20 14:20:04]

Please don't land changes when the tree is closed.

Tree being closed means there's active problems with the current build, so
committing more things in that state is just adding more problems for the
sheriff to deal with.

[Ilya Sherman, 2014-05-20 14:20:23]

Why was this landed with NOTREECHECKS=true?  That does not seem appropriate for
rolling v8.  It makes it harder to diagnose tree closures.

[Michael Achenbach, 2014-05-20 14:27:20]

On 2014/05/20 14:20:23, Ilya Sherman wrote:
> Why was this landed with NOTREECHECKS=true?  That does not seem appropriate
for
> rolling v8.  It makes it harder to diagnose tree closures.

Sorry for that. If our rolls don't make it into the canary we get hard
diagnostics problems on our side. And the tree was quite stale... + all tries
succeeded.

[Ilya Sherman, 2014-05-20 14:30:03]

On 2014/05/20 14:27:20, Michael Achenbach wrote:
> On 2014/05/20 14:20:23, Ilya Sherman wrote:
> > Why was this landed with NOTREECHECKS=true?  That does not seem appropriate
> for
> > rolling v8.  It makes it harder to diagnose tree closures.
> 
> Sorry for that. If our rolls don't make it into the canary we get hard
> diagnostics problems on our side. And the tree was quite stale... + all tries
> succeeded.

The best thing to do in this case is to help triage the tree failures.  That
way, problems can be diagnosed and fixed early, rather than when the history
grows muddy with unrelated commits.  (And, yes, it would be great if we had
24-hour sheriff coverage.  I think there was a thread on chromium-dev about this
recently, but I don't recall the outcome.)