flutter/bin/internal
engine-flutter-autoroll d48e6e433c
5c8147450 Clear layer cache in RasterCache::Clear (flutter/engine#6915) (#24596)
8d38417050...5c8147450d

git log 8d3841705030..5c8147450db5 --no-merges --oneline
5c8147450 Clear layer cache in RasterCache::Clear (flutter/engine#6915)


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.
2018-11-20 22:05:23 -05:00
..
engine.merge_method Switch engine.merge_method back to squash (#24319) 2018-11-13 17:12:36 -08:00
engine.version 5c8147450 Clear layer cache in RasterCache::Clear (flutter/engine#6915) (#24596) 2018-11-20 22:05:23 -05:00
goldens.version Add golden tests for Opacity with offset (#24253) 2018-11-14 15:00:39 -08:00
gradle_wrapper.version Make artifacts URLs configurable. (#13380) 2017-12-07 16:30:23 +01:00
material_fonts.version Make artifacts URLs configurable. (#13380) 2017-12-07 16:30:23 +01:00
README.md Add engine merge method configuration (#23953) 2018-11-07 13:06:38 -08:00
update_dart_sdk.ps1 update_dart_sdk.ps1: Fall back to Invoke-WebRequest if BITS fails (#19873) 2018-07-27 14:29:20 -07:00
update_dart_sdk.sh Update the URL to the recommend bug report (#23708) 2018-11-07 17:12:35 -08:00

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.