Master fails with Dart VM version: 2.0.0-dev.39.0

[grouma]

Failures appear to be Dart2JS related. Likely need to use the old frontend. See https://travis-ci.org/dart-lang/test/builds/354771199

[natebosch]

Using the old frontend is a good temporary fix to get unblocked. Longer term we'll want to make sure we're using arguments compatible with the latest Dart2Js approach.

[nex3]

I believe this is caused by dart-lang/sdk#32561, which means it should be fixed with the next dev SDK roll.

[natebosch]

Can we rely on PackageResolver.current.processArgument always choosing --package instead of --package-root?

I wasn't sure if all the failures where with --pub-serve or not

[nex3]

Can we rely on PackageResolver.current.processArgument always choosing --package instead of --package-root?

As long as it never depends on transformed code, it should be fine. If it is being run using a package root, there's not going to be any valid way of invoking dart2js.

I wasn't sure if all the failures where with --pub-serve or not

I didn't do a thorough check but it looked like they were at a glance.

[natebosch]

Initial workaround: #793

Still need to figure out a better long term solution

[nex3]

Once dart-lang/sdk#32633 is fixed (which it should be soon; it's marked P1 and there's a lot of activity around it) we'll be fine here.