
cebde437a1...2e06da3df9
git log cebde437a1b1..2e06da3df9cb --no-merges --oneline
2e06da3df Roll src/third_party/skia e7b1a13a1e2a..f7376330d11e (1 commits) (flutter/engine#6905)
46b2e1eed Roll src/third_party/skia 01979132133e..e7b1a13a1e2a (1 commits) (flutter/engine#6904)
dccbf9f41 Roll src/third_party/skia e22505b4f07f..01979132133e (1 commits) (flutter/engine#6902)
3114206a6 Roll src/third_party/skia def9bcecd994..e22505b4f07f (1 commits) (flutter/engine#6901)
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.
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.