[flutter_releases] Flutter beta 3.24.0-0.1.pre Engine Cherrypicks#54003
Conversation
|
This pull request was opened from and to a release candidate branch. This should only be done as part of the official Flutter release process. If you are attempting to make a regular contribution to the Flutter project, please close this PR and follow the instructions at Tree Hygiene for detailed instructions on contributing to Flutter. Reviewers: Use caution before merging pull requests to release branches. Ensure the proper procedure has been followed. |
|
I am not entirely sure if these test rely on main or the specific branch, and the only recent commit that I can find that may be related is: 8bcf638 cherry-picking for science, will revert afterward. Any ideas @christopherfujino? CC: @matanlurey |
…3539) ... and use it in `engine_tool` to prove everything is working, i.e. on CI and elsewhere. Partial work towards flutter/flutter#147883. Supersedes and closes flutter#51782 (which was a prototype). See also: - https://flutter.dev/go/pub-workspace, the design doc on the feature. - dart-lang/pub-dev#7762, an example PR. I'll probably end up moving the inline docs in `pubspec.yaml` to a `docs/*.md` once that's a thing.
…lutter#53539)" This reverts commit 8c1dd2f.
|
We should add a failure reason to this expectation: 8bcf638#diff-4b985d2a9688539b821af5a865e52e7e4eb2ef4cb6784229ef304feb33c7099dR68 |
|
My guess would be that this test is getting confused due to buildmoot-related directory shifting combined with infra caching issues(?). But yeah this test should definitely print more info when it fails. |
Flutter beta 3.24.0-0.1.pre Engine
Scheduled Cherrypicks
Infrastructure Issues
Tracked in flutter/flutter#152118