engine-flutter-autoroll 697a2a828f
Roll engine d4d4883216fd..b68f7e72aa71 (7 commits) (#29776)
d4d4883216...b68f7e72aa

git log d4d4883216fd1c1dfc17d41418a960c002cfff57..b68f7e72aa71eb75969bd674d78a5b40ee5ed89f --no-merges --oneline
b68f7e72a Allow specifying an alternate Mac host SDK. (flutter/engine#8249)
3df694300 Roll src/third_party/dart cabaa78cc5..ba0147ac07 (3 commits) (flutter/engine#8248)
69c4d82f5 Roll src/third_party/skia d6ab77a2e20f..19fb3971bca5 (17 commits) (flutter/engine#8245)
06635d38a Mirror Android platform views a11y tree in the Flutter a11y tree. (flutter/engine#8237)
28433c513 FlutterJNI no longer asserts it is attached when dispatching platform messages and instead fizzles with a warning if not attached. Not sure what root cause of issue is, but this is necessary to avoid crashes. (flutter/engine#8246)
1addfb596 Roll src/third_party/dart 5e9df35a57..cabaa78cc5 (36 commits) (flutter/engine#8244)
13e3b7101 Roll src/third_party/skia a695da930510..d6ab77a2e20f (11 commits) (flutter/engine#8243)

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 (liyuqian@google.com), and stop
the roller if necessary.
2019-03-21 21:54:41 -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.