Adds `DartOptions` to generic method syntax tests (updated CL).

Adds `DartOptions` to generic method syntax tests (updated CL).

This CL was landed and reverted. The bot failures caused by the first
landing of this CL turned out to be caused by checked mode execution.
This is an adjustment of that CL which marks the relevant tests as
failing. The underlying issue is that the compiler phases after
resolution do not expect to receive method type variables, only class
type variables; that will be addressed in a separate CL.

R=floitsch@google.com, johnniwinther@google.com

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

[eernst, 2016-05-10 13:50:21]

eernst@google.com changed reviewers:
+ johnniwinther@google.com

[eernst, 2016-05-10 13:50:22]

Marking some checked mode tests of generic method syntax as failing.

The actual failure is 'Crash', and status files do have that outcome; should I
use that?

[eernst, 2016-05-10 14:28:17]

On 2016/05/10 13:50:22, eernst wrote:
> Marking some checked mode tests of generic method syntax as failing.
> 
> The actual failure is 'Crash', and status files do have that outcome; should I
> use that?

Got confirmation that 'Crash' is the right status for an internal error.

[floitsch, 2016-05-10 15:30:59]

floitsch@google.com changed reviewers:
+ floitsch@google.com

[floitsch, 2016-05-10 15:30:59]

LGTM.

[Johnni Winther, 2016-05-11 07:40:56]

lgtm

[eernst, 2016-05-11 07:46:43]

Description was changed from

==========
Adds `DartOptions` to generic method syntax tests (updated CL).

This CL was landed and reverted. The bot failures caused by the first
landing of this CL turned out to be caused by checked mode execution.
This is an adjustment of that CL which marks the relevant tests as
failing. The underlying issue is that the compiler phases after
resolution do not expect to receive method type variables, only class
type variables; that will be addressed in a separate CL.
==========

to

==========
Adds `DartOptions` to generic method syntax tests (updated CL).

This CL was landed and reverted. The bot failures caused by the first
landing of this CL turned out to be caused by checked mode execution.
This is an adjustment of that CL which marks the relevant tests as
failing. The underlying issue is that the compiler phases after
resolution do not expect to receive method type variables, only class
type variables; that will be addressed in a separate CL.

R=floitsch@google.com, johnniwinther@google.com

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

[eernst, 2016-05-11 07:46:45]

Committed patchset #3 (id:40001) manually as
7da48f3a95a395f80a04f4df2010bd6e8a4bc502 (presubmit successful).