engine-flutter-autoroll 4673724e41
Roll engine 6061b804e359..f6526c0cf8a3 (7 commits) (#49799)
6061b804e3...f6526c0cf8

git log 6061b804e359..f6526c0cf8a3 --first-parent --oneline
2020-01-30 skia-flutter-autoroll@skia.org Roll src/third_party/skia 25bcd6a6215e..8f44c3504ca6 (2 commits) (flutter/engine#16243)
2020-01-30 skia-flutter-autoroll@skia.org Roll src/third_party/skia 24ed75db12ba..25bcd6a6215e (5 commits) (flutter/engine#16234)
2020-01-30 chinmaygarde@google.com Make output of run_tests.py easier to understand. (flutter/engine#16229)
2020-01-30 skia-flutter-autoroll@skia.org Roll fuchsia/sdk/core/mac-amd64 from c3sk5... to MK0YU... (flutter/engine#16221)
2020-01-30 chinmaygarde@google.com Remove buggy test to check if tasks can be posted on all native threads recursively from the emebdder. (flutter/engine#16214)
2020-01-30 chris@bracken.jp Correct the Fuchsia licenses golden file (flutter/engine#16215)
2020-01-30 skia-flutter-autoroll@skia.org Roll src/third_party/skia a2a0c8a2c475..24ed75db12ba (12 commits) (flutter/engine#16216)


If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC cbracken@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
2020-01-30 12:32:41 -05:00
..
2019-11-27 15:04:02 -08:00
2019-11-27 15:04:02 -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.