Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Windows framework_tests_widgets_leak_tracking is 2.13% flaky #168050

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.

Sign up for GitHub

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

Jump to bottom
Open
fluttergithubbot opened this issue Apr 30, 2025 · 1 comment
Open

Windows framework_tests_widgets_leak_tracking is 2.13% flaky #168050

fluttergithubbot opened this issue Apr 30, 2025 · 1 comment
Assignees
@Piinks
Labels
c: flake Tests that sometimes, but not always, incorrectly pass P1 High-priority issues at the top of the work list team-framework Owned by Framework team triaged-framework Triaged by Framework team

Comments

@fluttergithubbot
Copy link
Contributor

The post-submit test builder Windows framework_tests_widgets_leak_tracking had a flaky ratio 2.13% for the past (up to) 100 commits, which is above our 2.00% threshold.

One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Windows%20framework_tests_widgets_leak_tracking/2380
Commit: 39d8d41

Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Windows%20framework_tests_widgets_leak_tracking/2380
https://ci.chromium.org/ui/p/flutter/builders/prod/Windows%20framework_tests_widgets_leak_tracking/2369

Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Windows%20framework_tests_widgets_leak_tracking

Please follow https://github.com/flutter/flutter/blob/master/docs/infra/Reducing-Test-Flakiness.md#fixing-flaky-tests to fix the flakiness and enable the test back after validating the fix (internal dashboard to validate: go/flutter_test_flakiness).
@fluttergithubbot fluttergithubbot added c: flake Tests that sometimes, but not always, incorrectly pass P0 Critical issues such as a build break or regression team-framework Owned by Framework team labels Apr 30, 2025
@justinmc justinmc added the triaged-framework Triaged by Framework team label May 6, 2025
@fluttergithubbot
Copy link
Contributor Author

[prod pool] flaky ratio for the past (up to) 100 commits between 2025-04-30 and 2025-05-06 is 0.00%. Flaky number: 0; total number: 99.

@Piinks Piinks added P1 High-priority issues at the top of the work list and removed P0 Critical issues such as a build break or regression labels May 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Piinks Piinks

Labels
c: flake Tests that sometimes, but not always, incorrectly pass P1 High-priority issues at the top of the work list team-framework Owned by Framework team triaged-framework Triaged by Framework team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@justinmc @Piinks @fluttergithubbot