engine-flutter-autoroll 8ea8b18fb9
Roll engine 01b4f4e28065..31a7f4d5205d (2 commits) (#27301)
01b4f4e280...31a7f4d520

git log 01b4f4e280659a7333a77a570ff32122a2d947ad..31a7f4d5205df9d73fcdc148940d65d0efe55d95 --no-merges --oneline
31a7f4d52 Roll src/third_party/dart 2632e201b7..71bee8f05e (1 commits) 71bee8f05e Fix serializing procdure when realClass is Object from dart:core.
ed3ed9bc9 Roll src/third_party/skia c749f3bfd0e3..673a048b209c (1 commits) (flutter/engine#7639)

The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff (dnfield@google.com), and stop
the roller if necessary.
2019-01-30 14:29:40 -05:00
..

Dart SDK dependency

The bin/internal/engine.version file controls which version of the Flutter engine to use. The file contains the commit hash of a commit in the https://github.com/flutter/engine repository. That hash must have successfully been compiled on https://build.chromium.org/p/client.flutter/ and had its artifacts (the binaries that run on Android and iOS, the compiler, etc) successfully uploaded to Google Cloud Storage.

The /bin/internal/engine.merge_method file controls how we merge a pull request created by the engine auto-roller. If it's squash, there's only one commit for a pull request no matter how many engine commits there are inside that pull request. If it's rebase, the number of commits in the framework is equal to the number of engine commits in the pull request. The latter method makes it easier to detect regressions but costs more test resources.