Revert of Update V8 to version 4.4.7.

Revert of Update V8 to version 4.4.7. (patchset #1 id:1 of https://codereview.chromium.org/1076733002/)

Reason for revert:
Broke clang/win waterfall. https://codereview.chromium.org/1073903002/ fixes this, but I'd prefer if the bot wasn't red until that makes it into chromium.

Original issue's description:
> Update V8 to version 4.4.7.
> 
> Summary of changes available at:
> https://chromium.googlesource.com/v8/v8/+log/ca9f7433..1cb04a8e
> 
> Please follow these instructions for assigning/CC'ing issues:
> https://code.google.com/p/v8-wiki/wiki/TriagingIssues
> 
> TBR=hablich@chromium.org,machenbach@chromium.org,yangguo@chromium.org,vogelheim@chromium.org
> BUG=
> 
> Committed: https://crrev.com/d5d071430ce150bc1aec08291c51c70673878973
> Cr-Commit-Position: refs/heads/master@{#324410}

TBR=hablich@chromium.org,machenbach@chromium.org,vogelheim@chromium.org,yangguo@chromium.org,v8-autoroll@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=

[Nico, 2015-04-09 19:54:35]

Created Revert of Update V8 to version 4.4.7.

[commit-bot: I haz the power, 2015-04-09 19:55:44]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1071273004/1

[commit-bot: I haz the power, 2015-04-09 19:56:51]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-04-09 19:56:52]

Failed to apply patch for DEPS:
While running git apply --index -3 -p1;
  error: patch failed: DEPS:47
  error: repository lacks the necessary blob to fall back on 3-way merge.
  error: DEPS: patch does not apply

Patch:       DEPS
Index: DEPS
diff --git a/DEPS b/DEPS
index
6498632064f595a731cca64a5b0567141064651c..9a1304c9f5fc32ff32e6ae7f557d89eb6b8ac6aa
100644
--- a/DEPS
+++ b/DEPS
@@ -47,7 +47,7 @@
   # the commit queue can handle CLs rolling Skia
   # and V8 without interference from each other.
   'v8_branch': 'trunk',
-  'v8_revision': '1cb04a8ed49251c1c1e36d0ded0f5df9be4ed27c',
+  'v8_revision': 'ca9f7433e52bda6982f38506ace9f4df921df425',
   # Three lines of non-changing comments so that
   # the commit queue can handle CLs rolling WebRTC
   # and V8 without interference from each other.

[Nico, 2015-04-09 20:57:20]

Gah!

[Michael Achenbach, 2015-04-09 21:00:35]

Where is this bot and why is it not covered by the CQ?

I don't see any red tree closer. Furthermore, since this roll there landed two
more...

Generally I'd prefer to cherry-pick the v8-side fix or maybe a revert of the
culprit onto a roll, because reverting several v8 rolls costs us the canary
coverage for a day.

[Michael Achenbach, 2015-04-09 21:08:07]

I'll cherry-pick the fix onto the current roll.

[Nico, 2015-04-09 21:08:54]

(we talked on chat, all sorted out)

On Thu, Apr 9, 2015 at 2:00 PM, <machenbach@chromium.org> wrote:

> Where is this bot and why is it not covered by the CQ?
>
> I don't see any red tree closer. Furthermore, since this roll there landed
> two
> more...
>
> Generally I'd prefer to cherry-pick the v8-side fix or maybe a revert of
> the
> culprit onto a roll, because reverting several v8 rolls costs us the canary
> coverage for a day.
>
> https://codereview.chromium.org/1071273004/
>

To unsubscribe from this group and stop receiving emails from it, send an email
to chromium-reviews+unsubscribe@chromium.org.