engine-flutter-autoroll e4515824a1
Roll engine 134b65ec6034..e52287a1b557 (3 commits) (#26027)
134b65ec60...e52287a1b5

git log 134b65ec6034cdd9823ed5631df248d27870306e..e52287a1b5572c73b19d085ccbe404f0aeddb5f6 --no-merges --oneline
e52287a1b Fix typo clas -> class (flutter/engine#7360)
80c19b6b1 Roll src/third_party/skia 8966b55644c2..3b7e65107f67 (3 commits) (flutter/engine#7361)
beed0c455 Roll src/third_party/skia fdde2926df92..8966b55644c2 (1 commits) (flutter/engine#7359)

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@chromium.org), and stop
the roller if necessary.
2019-01-03 16:23:28 -05:00
..
2018-12-18 20:36:35 -08: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.