engine-flutter-autoroll b5723ecf16
Roll engine 2940812ab26a..134b65ec6034 (9 commits) (#26022)
2940812ab2...134b65ec60

git log 2940812ab26a9dac772459888f1e79389bedb977..134b65ec6034cdd9823ed5631df248d27870306e --no-merges --oneline
134b65ec6 Roll src/third_party/skia aae6ae39a356..fdde2926df92 (1 commits) (flutter/engine#7358)
f97edf2ac Roll src/third_party/skia 96345a23dfa9..aae6ae39a356 (1 commits) (flutter/engine#7357)
d051c47e5 Roll src/third_party/skia bc84adceaada..96345a23dfa9 (2 commits) (flutter/engine#7356)
15fcba4d8 Roll src/third_party/skia d0d5bb8c8500..bc84adceaada (6 commits) (flutter/engine#7355)
4d353de49 Preparing to remove SK_SUPPORT_LEGACY_PAINT_TEXTMEASURE (flutter/engine#7354)
54d7c4256 Paint all backgrounds first to prevent overlap (flutter/engine#7287)
0ad16dd10 Roll src/third_party/skia 279b65ddb5a3..d0d5bb8c8500 (12 commits) (flutter/engine#7353)
8cca33aea Give more control over when dynamic patches get downloaded and installed. (flutter/engine#7327)
2d291c7ff Roll src/third_party/skia 8f37ce5b9f2c..279b65ddb5a3 (6 commits) (flutter/engine#7350)

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 (amirha@chromium.org), and stop
the roller if necessary.
2019-01-03 14:55:29 -05:00
..
2018-12-18 20:36: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.