engine-flutter-autoroll 33f8030b32
Roll engine 498bbd5ef9c1..00e4abff84a6 (2 commits) (#24372)
498bbd5ef9...00e4abff84

git log 498bbd5ef9c1..00e4abff84a6 --no-merges --oneline
00e4abff8 Roll src/third_party/skia 44764000b49c..7d2aae3165a2 (1 commits) (flutter/engine#6861)
2c6be93fa Clean up stale cache entries in Skia's GrContext (flutter/engine#6859)


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-14 23:06:49 -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.