New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement a flutter
roller for flutter/plugins
#93811
Comments
This is what skia auto-rollers do with the engine->framework and plugins->framework. Sending an email to the skia team to get more details. |
This uses a pinned version from a file instead of `master` when checking out Flutter for `master` channel testing in Cirrus. Currently it's a static version, but this will be updated by an auto-roller. This uses a version of `master` from several days ago to avoid the current tree breakage due to flutter/flutter#96661 This will not affect LUCI tests; that will require a separate recipe change. Part of flutter/flutter#93811
This is now implemented for flutter/plugins for
|
Update LUCI to match recent Cirrus change, using a pinned version of master instead of latest master. Part of flutter/flutter#93811
Updates to match the recent change in flutter/plugins, to use a pinned version of master instead of the latest version. This uses the last version of master that passed post-submit tests due to a current out-of-band failure in golden tests. This affects both the Cirrus tests and the Windows LUCI tests. Part of flutter/flutter#93811
Creates a target file for a Flutter master pin autoroller. This is currently unused, but creating it allows setting up the autoroller. Prepares for flutter#554 Part of flutter/flutter#93811
Creates a target file for a Flutter master pin autoroller. This is currently unused, but creating it allows setting up the autoroller. Prepares for #554 Part of flutter/flutter#93811
Update LUCI to match recent Cirrus change, using a pinned version of master instead of latest master. Part of flutter/flutter#93811
Updates to match the recent change in flutter/plugins, to use a pinned version of master instead of the latest version. This uses the last version of master that passed post-submit tests due to a current out-of-band failure in golden tests. This affects both the Cirrus tests and the Windows LUCI tests. Part of flutter/flutter#93811
Switch from using the the latest stable version to using a pinned stable version, just as we do for master. Fixes flutter/flutter#93811 Fixes the flutter/plugins half of flutter/flutter#106900
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
Currently flutter/plugins uses whatever the latest
stable
andmaster
are when running tests. This means that:flutter
change break us in the meantime, causing it to be impossible to ever make that test pass for that commit (because fixing such breakage often requires a commit in flutter/plugins). This is especially problematic for our auto-publish, which can only run when all tests are green.To prevent this, we should use pinned versions of
master
andstable
, with auto-rollers that update them to the latest versions on a regular basis. Themaster
version would be expected to commit more or less all the time, as with the flutter/engine->flutter/flutter roller, while thestable
version would usually not need to do anything./cc @godofredoc Are there pointers to what's involved in setting up an auto-roller? (The read-from-a-pinned-version for CI is something I could implement pretty easily.)
The text was updated successfully, but these errors were encountered: