engine-flutter-autoroll e189f0c27f
99d848a9986cb376b9858e2b7345fcea6637ff51 (#24350)
114d33d3ca...99d848a998

git log 114d33d3caa2..99d848a9986c --no-merges --oneline
99d848a99 Roll src/third_party/skia b45b53f01cf3..7f2b6fa66575 (1 commits) (flutter/engine#6855)


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, who should
be CC'd on the roll, and stop the roller if necessary.
2018-11-14 15:17:49 -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.