-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Move Linux coverage back to bringup
#174171
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
Conversation
|
Detected the If you add the The "Merge" button is also unlocked. To bypass presubmits as well as the tree status, press the GitHub "Add to Merge Queue". |
1 similar comment
This comment was marked as duplicate.
This comment was marked as duplicate.
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.
Code Review
This pull request moves the Linux coverage test to bringup mode to handle its flakiness. My feedback is to add a TODO with a tracking issue for this flaky test, as per the repository's guidelines for managing test flakiness. This will help ensure the issue is not forgotten.
flutter/flutter@960d107...d2ac021 2025-08-21 [email protected] [web] Delete unused utils (flutter/flutter#174160) 2025-08-21 [email protected] Directly generate a Mach-O dynamic library using gen_snapshot. (flutter/flutter#171626) 2025-08-21 [email protected] Update the text input team's issue triage query (flutter/flutter#173999) 2025-08-21 [email protected] Roll Fuchsia Linux SDK from V1A1J6uXZ62Q10i9u... to Z-ZaFQ7jAqJ1OrIBf... (flutter/flutter#174170) 2025-08-21 [email protected] whitespace (flutter/flutter#174210) 2025-08-21 [email protected] Add review agent style guidelines to .gemini/styleguide.md (flutter/flutter#174000) 2025-08-20 [email protected] Move `Linux coverage` back to bringup (flutter/flutter#174171) 2025-08-20 [email protected] Engine build setup for Android RISCV64. (flutter/flutter#173672) 2025-08-20 [email protected] [ios][tools] do not print out bonjour key not found in non-verbose mode (flutter/flutter#174001) 2025-08-20 [email protected] Make sure that an Autocomplete doesn't crash in 0x0 environment (flutter/flutter#172732) 2025-08-20 [email protected] Migrate some files to use `WidgetStateProperty` (flutter/flutter#174109) 2025-08-20 [email protected] Fix `onSelect` called twice in `DropdownMenuFormField` (flutter/flutter#174053) 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 Please CC [email protected],[email protected] on the revert to ensure that a human is aware of the problem. To file a bug in Packages: 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
Because this only runs every 6 commits, it being flaky takes a long time to recover. It's not a priority to keep green and un-flaky at the moment.
Because this only runs every 6 commits, it being flaky takes a long time to recover. It's not a priority to keep green and un-flaky at the moment.
Because this only runs every 6 commits, it being flaky takes a long time to recover. It's not a priority to keep green and un-flaky at the moment.
Because this only runs every 6 commits, it being flaky takes a long time to recover. It's not a priority to keep green and un-flaky at the moment.
Because this only runs every 6 commits, it being flaky takes a long time to recover. It's not a priority to keep green and un-flaky at the moment.
Because this only runs every 6 commits, it being flaky takes a long time to recover. It's not a priority to keep green and un-flaky at the moment.
Because this only runs every 6 commits, it being flaky takes a long time to recover.
It's not a priority to keep green and un-flaky at the moment.