f3ec767458...a850016454
git log f3ec767458f12bb3099248fdc57d6c0d1051f042..a850016454f6d33da64d03dbd1ea71fd0fac299f --no-merges --oneline
a85001645 Roll src/third_party/skia bb482ab871a2..73cc4e8d5fcf (1 commits) (flutter/engine#8395)
aba61e8fb Roll src/third_party/skia 5ee611b26f23..bb482ab871a2 (4 commits) (flutter/engine#8394)
82071e916 Don't access a11y APIs with reflection starting Android P. (flutter/engine#8393)
d9f16111a Roll src/third_party/skia acb4829c1be4..5ee611b26f23 (1 commits) (flutter/engine#8392)
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 (bmparr@google.com), and stop
the roller if necessary.
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.