
e9eae9a1af...4f54a1dd94
git log e9eae9a1af77400d02c498f0ad943f2858845398..4f54a1dd944497bd1ec0f2acca22ff9fbd8b377a --no-merges --oneline
4f54a1dd9 Roll src/third_party/skia c1a9feb6f06e..5800f2e8a920 (2 commits) (flutter/engine#8022)
75e2b4702 Roll src/third_party/skia c6671be0ea75..c1a9feb6f06e (2 commits) (flutter/engine#8021)
b44a9305c Roll src/third_party/skia 1b9f889628e0..c6671be0ea75 (1 commits) (flutter/engine#8020)
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 (garyq@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.