engine-flutter-autoroll 8d80762cc1
Roll engine 23b7e29f043f..6d405201fa51 (5 commits) (#27065)
23b7e29f04...6d405201fa

git log 23b7e29f043fbf69c175450a21b81028deffa470..6d405201fa51c26b1d5211aa9c857c4286d165af --no-merges --oneline
6d405201f Add lcov coverage file generation. (flutter/engine#7579)
f4bdb9488 Roll src/third_party/skia 7fe360cbc01e..7150513754f5 (10 commits) (flutter/engine#7578)
ce44132a1 This is an automated pull request which will automatically merge once checks pass. (flutter/engine#7573)
0dedb56d2 [embedder] Avoid looking for the kernel binary in AOT builds. (flutter/engine#7577)
1dc01adfa Allow generating coverage reports for all unit-tests in the engine. (flutter/engine#7576)

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 (jsimmons@google.com), and stop
the roller if necessary.
2019-01-25 01:42:39 -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.