67aadb6206...209250da1b
git log 67aadb62068ad251c79affa2ae68d6579d8e2d93..209250da1bb31dd3cc56e9a96274e62c7d7d39ee --no-merges --oneline
209250da1 When running in AOT modes create a flutter_assets directory that can be used as the bundle path (flutter/engine#9306)
159383839 Handle Fuchsia SDK in license tool + roll SDK (flutter/engine#9302)
e66118bcb Roll src/third_party/skia 81756e4cae95..b9416caa367a (6 commits) (flutter/engine#9305)
7bb5b9aea Wire up Swiftshader based OpenGL ES unit-tests on hosts. (flutter/engine#9264)
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 (liyuqian@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.