There seems to be issues with mockito package:

╰─➤  bin/flutter doctor                                                                                                               130 ↵
Building flutter tool...
The current Dart SDK version is 2.1.0-dev.0.0.flutter-be6309690f.

Because flutter_tools depends on mockito >=0.8.1 <3.0.0-beta+3 which requires SDK version >=1.0.0 <2.0.0-∞, version solving failed.
Error: Unable to 'pub upgrade' flutter tool. Retrying in five seconds...

Turns out Siva's roll in the engine wasn't further rolled into flutter/flutter yet.

Doing this will require upgrading all 3rd party packages in pubspec files to be compatible with Dart 2, since this roll includes a new version number, namely 2.1.0-dev.0.0.

I've tried to find all the necessary package upgrades and filed issues for:

• Please publish a new version, which is compatible with Dart SDK ^2.1.0 google/process.dart#32
• https://github.com/google/platform.dart/issues/17
• https://github.com/google/file.dart/issues/105

So far.

The SEGV crash in the flutter_tester binary crashed very deeply inside the Dart VM when doing a constant evaluation inside package:test code.

After debugging this for a while it became clear that this is due to a missing platform file, which caused the VM to fall back to code paths which it should never fall back to in a Dart 2.0 world.

The root cause was flutter/engine@a84b210 which renamed the platform file the flutter_tester binary expects, but a corresponding change in flutter wasn't done yet.

Since the engine->flutter roll also brings in new skia changes, I've made flutter/goldens#11 to update the goldens.

still LGTM

The existing redness on the flutter dashboard needs to be investigated, e.g. I can see e.g. stderr: > Java heap space in this log, but I think it makes sense to land this now, since there are already more engine commits waiting to be rolled in. Hope that this is ok.