mirror of
https://github.com/flutter/flutter.git
synced 2026-02-06 03:39:05 +08:00
This pulls in the 4 commits below:
8be72094d...c9cbc600e
2025-04-24 greg@zulip.com Bump Zulip pin to update sliver z-order tests
(flutter/tests#456) 2025-04-17
43759233+kenzieschmoll@users.noreply.github.com Revert "Disable
flutter_devtools.test" (flutter/tests#455) 2025-04-15 aam@google.com
Update zulip hash to pick up version that can be analyzed cleanly.
(flutter/tests#453) 2025-04-15 bkonyi@google.com Disable
flutter_devtools.test (flutter/tests#452)
(using the command from 5ce5251e4 / #162763 to make the log).
The two changes from 2025-04-15 had been here since db68c950c (#16721),
but then it looks like they were accidentally reverted earlier today by
417f47fda (#165596).
The change from 04-17 doesn't appear to have made it here to
flutter/flutter yet.
The latest change just went into flutter/tests today and is why I'm
making this PR.
## Pre-launch Checklist
- [x] I read the [Contributor Guide] and followed the process outlined
there for submitting PRs.
- [x] I read the [Tree Hygiene] wiki page, which explains my
responsibilities.
- [x] I read and followed the [Flutter Style Guide], including [Features
we expect every widget to implement].
- [x] I signed the [CLA].
- [ ] I listed at least one issue that this PR fixes in the description
above.
- [ ] I updated/added relevant documentation (doc comments with `///`).
- [ ] I added new tests to check the change I am making, or this PR is
[test-exempt].
- [x] I followed the [breaking change policy] and added [Data Driven
Fixes] where supported.
- [x] All existing and new tests are passing.
If you need help, consider asking for advice on the #hackers-new channel
on [Discord].
<!-- Links -->
[Contributor Guide]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview
[Tree Hygiene]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md
[test-exempt]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests
[Flutter Style Guide]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md
[Features we expect every widget to implement]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement
[CLA]: https://cla.developers.google.com/
[flutter/tests]: https://github.com/flutter/tests
[breaking change policy]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes
[Discord]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md
[Data Driven Fixes]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md
customer_testing
This tool checks out https://github.com/flutter/tests at the commit SHA
specified in tests.version, and runs the tests registered to
verify that end-user apps and libraries are working at the current tip-of-tree
of Flutter.
To (locally) test a specific SHA, use ci.dart:
cd dev/customer_testing
dart ci.dart [sha]
Or, to update the SHA for our CI, edit and send a PR for
tests.version.