-
Notifications
You must be signed in to change notification settings - Fork 27.7k
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
Flutter stable framework 1.20.3 cherrypicks #64984
Flutter stable framework 1.20.3 cherrypicks #64984
Conversation
This pull request was opened against a branch other than master. Since Flutter pull requests should not normally be opened against branches other than master, I have changed the base to master. If this was intended, you may modify the base back to flutter-1.20-candidate.7. See the Release Process for information about how other branches get updated. Reviewers: Use caution before merging pull requests to branches other than master, unless this is an intentional hotfix/cherrypick. |
…). (flutter#64519) Added instructions on how to regenerate certificate too.
Fixes flutter#45075 Fixes flutter#57210 If an asset was included directly from the project root directory, then the same asset when copied to various output or ephemeral directories would also be picked up as an asset variant. This could cause assets to be recursively copied into asset/build/ephemeral directories, as each time it would run it would pick up all of the previous "variants". The solution is to include project ephemeral directories, in addition to the build directory.
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
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.
LGTM
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.
approved for branch. don't forget to sign the engine :)
Thanks for checking, I did already. |
@a14n please look for review, and also CLABot needs consent again :P |
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.
LGTM
@googlebot I consent |
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
LGTM |
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.
LGTM for time picker change
Re-running Update: passed on re-run, everything is green except for expected failures, which I've tracked in the description. |
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.
LGTM
Sorry, thought @jonahwilliams's was enough. |
Yeah, sorry, I should have been more clear. For extra safety I'm trying out getting multiple reviewers per cherry pick, starting this week. Speaking of which, @goderbauer could you verify the change to |
@christopherfujino - Michael is out this week; is there someone else who could LGTM the change to |
Ahh, thanks. In that case, I can LGTM it :) |
Merging with the failures all known and issues filed, see PR description for details. |
* Update engine hash to 1.20.3 * Re-enable image_list test with updated certificate(good for 3650 days). (flutter#64519) * [Material] Relanding fix to ensure time picker input mode lays out correctly in RTL (flutter#64097) * allow null in compute for weak mode (flutter#63515) * [flutter_tools] fix recursive asset variant issue (flutter#61129) * [flutter_tool] Handle Windows line endings in packages_test.dart (flutter#63806) * [flutter_tool] Fix some create_test.dart tests on Windows (flutter#63796) Co-authored-by: Alexander Aprelev <aam@google.com> Co-authored-by: Rami <2364772+rami-a@users.noreply.github.com> Co-authored-by: Alexandre Ardhuin <alexandre.ardhuin@gmail.com> Co-authored-by: Jonah Williams <jonahwilliams@google.com> Co-authored-by: Zachary Anderson <zanderso@users.noreply.github.com>
Scheduled Cherrypicks
d1bc06f032f9d6c148ea6b96b48261d6f545004f
021cf56fc97f96e0571bbb13d2c7a6d66de3beff
afc9509996b334b71f51f625125c232dce649606
741608a261e3b6ac3c36c7ad6cdf798f86733d07
Test/Infra-Only Cherrypicks
ed65f5e96cb2437e0315b65df0aba248e3896b45
packages_test.dart
1884920e30b8d82f2e6408aae1c2b780349d8d00
create_test.dart
f360d8b8e8a7909c65db0d82b5cb07ab4e7cc0ff
Presubmit Known Failures
Linux customer_testing
andWindows customer_testing
because of Pin all repos we clone from HEAD for CI #57062. In the cirrus config, this test was pinned and is green.Linux fuchsia-precache
because LUCI try-jobs still running latest recipes LUCI try jobs for release branches should use correct builder/recipes #53371.Postsubmit Known Failures
Windows Stable hostonly_devicelab_tests
known failure, these are still red on master but ignored by the build dashboard hostonly_devicelab_tests failing consistently on luci #64466.flutter/gallery
in tests #62983 this was pinned upstream in Pin gallery version #62986.customer_testing
Linux/Windows known failure, will be fixed by pinning repo checkout on LUCI Pin all repos we clone from HEAD for CI #57062fuchsia_precache
known failure, will be fixed by being able to skip tasks post-submit [infra] No way to skip builders per-branch on post-submit #64975