[test] Fix windows nosnap test expectations.

[test] Fix windows nosnap test expectations.

Now that we pass all these tests, we need to update the test
expectations.

TBR=machenbach@chromium.org

Committed: https://crrev.com/318d9f52fd968b1cc0bdc955843ab27abb7bacc4
Cr-Commit-Position: refs/heads/master@{#35295}

[Benedikt Meurer, 2016-04-06 10:02:00]

The CQ bit was checked by bmeurer@chromium.org

[commit-bot: I haz the power, 2016-04-06 10:02:13]

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

[Michael Achenbach, 2016-04-06 10:10:25]

The CQ bit was unchecked by machenbach@chromium.org

[Michael Achenbach, 2016-04-06 10:11:20]

Can it be that you miss a few? Note that the UI is showing only 10 failures with
nice links. More failures can be found in the stdio:
https://build.chromium.org/p/client.v8/builders/V8%20Win32%20-%20nosnap%20-%2...

[Michael Achenbach, 2016-04-06 10:12:32]

On 2016/04/06 10:11:20, Michael Achenbach wrote:
> Can it be that you miss a few? Note that the UI is showing only 10 failures
with
> nice links. More failures can be found in the stdio:
>
https://build.chromium.org/p/client.v8/builders/V8%20Win32%20-%20nosnap%20-%2...

E.g. pipe the whole stdio through | grep ===

[Michael Achenbach, 2016-04-06 10:15:06]

cat stdio | grep "=== mjsunit" | sort | uniq | awk '{ print $2 }'
mjsunit/es6/array-from
mjsunit/es6/classes-subclass-builtins
mjsunit/es6/computed-property-names-classes
mjsunit/es6/computed-property-names-object-literals-methods
mjsunit/es6/debug-stepin-generators
mjsunit/es6/destructuring
mjsunit/es6/destructuring-assignment
mjsunit/es6/generators-iteration
mjsunit/es6/generators-mirror
mjsunit/es6/generators-parsing
mjsunit/es6/generators-poisoned-properties
mjsunit/es6/generators-relocation
mjsunit/es6/generators-states
mjsunit/es6/iteration-semantics
mjsunit/es6/object-literals-method
mjsunit/es6/object-literals-super
mjsunit/es6/promises
mjsunit/es6/regress/regress-2681
mjsunit/es6/regress/regress-2691
mjsunit/es6/regress/regress-3280
mjsunit/es6/spread-array
mjsunit/es6/spread-call
mjsunit/es6/typedarray
mjsunit/es6/typedarray-from
mjsunit/harmony/function-sent
mjsunit/harmony/generators
mjsunit/harmony/iterator-close
mjsunit/harmony/regress/regress-4482
mjsunit/messages
mjsunit/regress-3225

[Benedikt Meurer, 2016-04-06 10:33:02]

The CQ bit was checked by bmeurer@chromium.org

[commit-bot: I haz the power, 2016-04-06 10:33:12]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1864013002/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1864013002/20001

[Michael Achenbach, 2016-04-06 11:38:04]

LGTM yea!

[commit-bot: I haz the power, 2016-04-06 11:39:43]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-04-06 11:40:30]

Description was changed from

==========
[test] Fix windows nosnap test expectations.

Now that we pass all these tests, we need to update the test
expectations.

TBR=machenbach@chromium.org
==========

to

==========
[test] Fix windows nosnap test expectations.

Now that we pass all these tests, we need to update the test
expectations.

TBR=machenbach@chromium.org

Committed: https://crrev.com/318d9f52fd968b1cc0bdc955843ab27abb7bacc4
Cr-Commit-Position: refs/heads/master@{#35295}
==========

[commit-bot: I haz the power, 2016-04-06 11:40:31]

Patchset 2 (id:??) landed as
https://crrev.com/318d9f52fd968b1cc0bdc955843ab27abb7bacc4
Cr-Commit-Position: refs/heads/master@{#35295}

[Michael Achenbach, 2016-04-06 12:30:39]

https://build.chromium.org/p/client.v8/builders/V8%20Win32%20-%20nosnap%20-%2...

But why???

[Michael Achenbach, 2016-04-06 12:34:46]

On 2016/04/06 12:30:39, Michael Achenbach wrote:
>
https://build.chromium.org/p/client.v8/builders/V8%20Win32%20-%20nosnap%20-%2...
> 
> But why???

Seems to be a random-seed specific flake :/