engine-flutter-autoroll 2ae1379995
Roll engine b10b8e899029..114d33d3caa2 (3 commits) (#24345)
b10b8e8990...114d33d3ca

git log b10b8e899029..114d33d3caa2 --no-merges --oneline
114d33d3c Set and unset accessibility flags even when re-entrant (flutter/engine#6853)
396402f5b Flush UserSettings to window (flutter/engine#6850)
1e7e676e4 Remove unused import (flutter/engine#6854)


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 11:07:51 -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.