Fix vm-kernel status file after merging kernel.

Fix vm-kernel status file after merging kernel.

The buildbots run tests against the checked-in version of analyzer,
not the one in the pubspec, which is why the tests behave differently.

BUG=
R=kmillikin@google.com

Committed: https://github.com/dart-lang/sdk/commit/b0ffc26dab03b611de9171e8eebe3d58122c37d5

[asgerf, 2016-11-23 13:09:33]

asgerf@google.com changed reviewers:
+ kmillikin@google.com, kustermann@google.com, vegorov@google.com

[Kevin Millikin (Google), 2016-11-23 13:12:14]

lgtm

[kustermann, 2016-11-23 13:13:20]

I thought I changed that this morning in
https://github.com/dart-lang/sdk/commit/656be7a7aa11c2a61e357b879d05ed5a1c7d7350

[asgerf, 2016-11-23 13:16:05]

On 2016/11/23 13:13:20, kustermann wrote:
> I thought I changed that this morning in
>
https://github.com/dart-lang/sdk/commit/656be7a7aa11c2a61e357b879d05ed5a1c7d7350

You are right, I accidentally changed it back when I updated the status file in 
the merge.

When I ran the tests, I had previously done a "pub get" from the pkg/kernel
folder which made all the tests behave in the old way.

[asgerf, 2016-11-23 13:19:39]

Description was changed from

==========
Fix vm-kernel status file after merging kernel.

The buildbots run tests against the checked-in version of analyzer,
not the one in the pubspec, which is why the tests behave differently.

BUG=
==========

to

==========
Fix vm-kernel status file after merging kernel.

The buildbots run tests against the checked-in version of analyzer,
not the one in the pubspec, which is why the tests behave differently.

BUG=
R=kmillikin@google.com

Committed:
https://github.com/dart-lang/sdk/commit/b0ffc26dab03b611de9171e8eebe3d58122c37d5
==========

[asgerf, 2016-11-23 13:19:40]

Committed patchset #1 (id:1) manually as
b0ffc26dab03b611de9171e8eebe3d58122c37d5 (presubmit successful).