Repository navigation
[material_ui] Remove no-shuffle from dropdown test - #12528
Merged
auto-submit[bot] merged 1 commit intoAug 21, 2026
Merged
auto-submit[bot] merged 1 commit into
auto-submit[bot] merged 1 commit into
Conversation
github-actions
Bot
added
p: material_ui
triage-design
Contributor
Author
|
This doesn't need a pending changelog file since it only affects a test |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request removes the 'no-shuffle' tag and its associated explanatory comments from the 'packages/material_ui/test/dropdown_test.dart' test file, allowing the test to be run with randomized ordering. There are no review comments, and I have no feedback to provide.
10 tasks done
QuncCccccc
added
the
autosubmit
pull Bot
pushed a commit
to fucheng-guo-sun/flutter
that referenced
this pull request
Aug 24, 2026
…r#191578) flutter/packages@252bb33...df2ba94 2026-08-24 49699333+dependabot[bot]@users.noreply.github.com [dependabot]: Bump org.json:json from 20260719 to 20260814 in /packages/in_app_purchase/in_app_purchase_android/example/android/app (flutter/packages#12570) 2026-08-22 [email protected] Roll Flutter from c243752 to 65c9a8d (195 revisions) (flutter/packages#12554) 2026-08-21 [email protected] [pigeon] add modern concurrency support (flutter/packages#12382) 2026-08-21 [email protected] [material_ui] Remove no-shuffle in scrollbar test (flutter/packages#12527) 2026-08-21 [email protected] [material_ui] Remove no-shuffle from dropdown test (flutter/packages#12528) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/flutter-packages-flutter-autoroll Please CC [email protected] on the revert to ensure that a human is aware of the problem. To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of flutter/flutter#85160
Ported from flutter/flutter#186398
Pre-Review Checklist
[shared_preferences]///).If you need help, consider asking for advice on the #hackers-new channel on Discord.
Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the
gemini-code-assistbot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.Footnotes
Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩2