engine-flutter-autoroll 522dd30dc3
1baf08134 Roll src/third_party/skia a63cf8e80aa5..6bdfb6fba352 (1 commits) (flutter/engine#6911) (#24558)
a4afd19a97...1baf081343

git log a4afd19a97e2..1baf08134353 --no-merges --oneline
1baf08134 Roll src/third_party/skia a63cf8e80aa5..6bdfb6fba352 (1 commits) (flutter/engine#6911)


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-20 00:56:04 -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.