-
Notifications
You must be signed in to change notification settings - Fork 29.8k
Pin gallery version #62986
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
Pin gallery version #62986
Conversation
| // found in the LICENSE file. | ||
|
|
||
| /// The pinned version of flutter gallery, used for devicelab tests. | ||
| const String galleryVersion = 'a208eac6e6e8336ae9820e54c572c099231f1da2'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is awesome. Your PR LGTM.
My only question is if there is an official documented procedure for rolling the gallery here, and if it can be updated to reference this file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know. I'm asking right now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1, interested in how this works as gallery changes - don't we want master to test against the newest gallery? this seems more reasonable for branches than master (but I may be misunderstanding)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we always ask flutter/flutter:master to clone flutter/gallery:master, an error in Gallery might cause Flutter's build to fail. These tests always uses latest flutter/flutter:master.
I think the best way is to use a commit hash instead of a branch, and set up a process to roll it regularly. (But this is a future task.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@christopherfujino @pcsosinski
There isn't a process to roll the gallery version yet. It would be a good idea to add this process, some time in the future.
|
I can confirm these pass for me locally |
guidezpl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
_ ___ _____ __ __
| | / __|_ _| \/ |
| |_| (_ | | | | |\/| |
|____\___| |_| |_| |_|
pcsosinski
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would like to see some process around how we update this hash (who is responsible, how often, etc) to make sure we don't get stuck on an old version. thanks!
Agreed, I think establishing a roll process for the gallery should be a high priority. I recall at least once the Flutter framework build was broken because of a change that had already landed in the gallery repo, but hadn't been rolled. |
|
Is there any way we can move these tests to customer tests https://github.com/flutter/tests/blob/master/registry/flutter_gallery.test and out of Flutter proper? That is also pinning a SHA that already needs to roll. |
What are the differences between placing tests here vs. placing tests in https://github.com/flutter/tests/blob/master/registry/flutter_gallery.test? |
|
https://github.com/flutter/tests#flutter-tests
|
We also have gallery v1 benchmarks |
Description
Pin the version of
flutter/galleryin devicelab tests influtter/flutter.Related Issues
Closes #62983
Tests
No tests were added.
Checklist
Before you create this PR, confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]). This will ensure a smooth and quick review process.///).flutter_gallery_v2_chrome_run_testandflutter_gallery_v2_web_compile_test, and they are passing.flutter analyze --flutter-repo) does not report any problems on my PR.Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.
flutter_gallery_v2_chrome_run_testandflutter_gallery_v2_web_compile_test, and they are passing.