engine-flutter-autoroll 39597ce718
Roll engine 0f2ab22abb2c..4444c9cb6c9f (2 commits) (#34970)
0f2ab22abb...4444c9cb6c

git log 0f2ab22abb2c8744be7cd5054f7a7b2af65eacd9..4444c9cb6c9f1859c1807cff415cd716bb9612ff --no-merges --oneline
4444c9cb6 Roll src/third_party/skia 089f13f98286..6ce447a4ec20 (1 commits) (flutter/engine#9453)
552a72932 Roll src/third_party/skia 38daf0be45e4..089f13f98286 (2 commits) (flutter/engine#9451)

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 (amirha@google.com), and stop
the roller if necessary.
2019-06-24 03:39:55 -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.