engine-flutter-autoroll e8c2f2c7f8
Roll engine 319e1c5c1d1c..1c26bf8c4b55 (3 commits) (#26969)
319e1c5c1d...1c26bf8c4b

git log 319e1c5c1d1ce1f8f1f3f25c1c40df5be8033775..1c26bf8c4b55f4fa5f0d175768a1a0cc115c70b2 --no-merges --oneline
1c26bf8c4 Roll src/third_party/skia d562545e8a23..4f81bb73311d (1 commits) (flutter/engine#7561)
01c85da0f Roll src/third_party/skia 24120c2a32c6..d562545e8a23 (1 commits) (flutter/engine#7556)
299438728 Roll src/third_party/skia 325778b8884b..24120c2a32c6 (1 commits) (flutter/engine#7553)

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-01-23 12:49: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.