Skip initializing_formal_* tests on Dartium

Skip initializing_formal_* tests on Dartium

Apparently the VM does not get the --initializing-formal-access flag
set, which these tests need in order to pass.

TBR=terry

BUG=

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

[hausner, 2016-08-04 20:45:37]

Description was changed from

==========
Skip initializing_formal_* tests on Dartium

Apparently the VM does not get the --initializing-formal-access flag
set, which these tests need in order to pass.

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

to

==========
Skip initializing_formal_* tests on Dartium

Apparently the VM does not get the --initializing-formal-access flag
set, which these tests need in order to pass.

TBR=terry

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

[hausner, 2016-08-04 20:45:38]

hausner@google.com changed reviewers:
+ terry@google.com

[hausner, 2016-08-04 20:47:24]

Description was changed from

==========
Skip initializing_formal_* tests on Dartium

Apparently the VM does not get the --initializing-formal-access flag
set, which these tests need in order to pass.

TBR=terry

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

to

==========
Skip initializing_formal_* tests on Dartium

Apparently the VM does not get the --initializing-formal-access flag
set, which these tests need in order to pass.

TBR=terry

BUG=

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

[hausner, 2016-08-04 20:47:26]

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

[eernst, 2016-08-05 08:58:36]

On 2016/08/04 20:47:26, hausner wrote:
> Committed patchset #1 (id:1) manually as
> 6075a535473b8b8b71ac0d1cfc638be752f82169 (presubmit successful).

Just a tiny thing: Did you consider using `CompiletimeError` (or
`RuntimeError`, whatever it actually is) rather than `Skip` for the
initializing_formal_* tests in this particular configuration? The
purpose would be to automatically get a notification when that 
feature is made the default behavior and the `..Error` changes to a
successful run (same thing if the flag starts getting passed to the
vm). Otherwise someone would need to be lucky enough to remember
that these status entries can be deleted at that point. ;-)

[hausner, 2016-08-05 20:02:47]

Thanks for the suggestion. I did consider it, but thought that skipping is
better. Being more specific about the kind of failure has the potential to just
adding more noise and false positives. Also, all the test coverage that is
needed is already there in the command line VM test suites.