d5753ccd91
b188479981...b7dd1cdce9
git log b18847998196a29fe66cc025ce0f8c9d76db6b20..b7dd1cdce95aa5c097ee4f80fb65204e90a2e280 --no-merges --oneline
b7dd1cdce ios-unit-tests: Fixed ocmock system header search paths. (flutter/engine#9469)
a6e5b10f2 Forgot a usage of a variable in our script. (flutter/engine#9467)
183a76b38 Added shebangs to ios unit test scripts. (flutter/engine#9464)
56954457a Don't hang to a platform view's input connection after it's disposed (flutter/engine#9423)
45ef6c8cf Remove unused/unimplemented shell constructor (flutter/engine#9459)
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 (amirha@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.