
5722a9685e...abbc34e148
git log 5722a9685e3cba77649ba5257a91ed21933ca063..abbc34e1482d0a118a84040933f61cfa42a1fb5f --no-merges --oneline
abbc34e14 Roll src/third_party/skia 82223aae39b7..2ee498c6749a (2 commits) (flutter/engine#7454)
f817343a7 Roll src/third_party/skia e548161aba5b..82223aae39b7 (3 commits) (flutter/engine#7453)
cd0169ae2 Roll src/third_party/skia c334df71b8f9..e548161aba5b (1 commits) (flutter/engine#7452)
377ff1975 Roll src/third_party/dart f0c7d971c472066e29a949aab8826c204cfbaf35..f81dd1da9f9f879c17dda7b20a2572fa5549f3dd (2 commits) f81dd1da9f Handle super* in ir/impact.dart 99a9ae66c3 [dart2js] run dartfmt --fix-doc-comments on stragglers
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 (cbracken@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.