engine-flutter-autoroll cd814eb3fb
Roll engine e1599ccd3f89..e3772232c2d2 (2 commits) (#33082)
e1599ccd3f...e3772232c2

git log e1599ccd3f89943a11c89ac8a31cc7d3edd72073..e3772232c2d24c174beac7ef03dff63907cdda46 --no-merges --oneline
e3772232c Roll src/third_party/dart 82c8c78739..b48c8b1d1c (5 commits) (flutter/engine#9021)
14912e8e1 Roll src/third_party/skia d93ee53affd3..dbc3caaf6c3d (9 commits) (flutter/engine#9024)

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 (jsimmons@google.com), and stop
the roller if necessary.
2019-05-20 20:21:17 -04: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.