engine-flutter-autoroll b5e0973591
Roll engine 85492c3e804a..4812a2af115c (3 commits) (#27518)
85492c3e80...4812a2af11

git log 85492c3e804a6f6bf06275ed49c103ac6548be87..4812a2af115ce81c0ad1dec8680fdf9ea7dd4fc4 --no-merges --oneline
4812a2af1 DCHECK that clip layer's behavior isn't none (flutter/engine#7659)
eaae8a67b Retained rendering in Fuchsia PhysicalShapeLayer (flutter/engine#6558)
194608290 Move Brightness definition to dart:ui (#27479) (flutter/engine#7678)

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 (dnfield@google.com), and stop
the roller if necessary.
2019-02-04 20:16:28 -05: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.