Skip to content
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

Linux_pixel_7pro draw_atlas_perf__timeline_summary is 2.04% flaky #146870

Closed
fluttergithubbot opened this issue Apr 17, 2024 · 4 comments
Closed
Assignees
Labels
c: flake Tests that sometimes, but not always, incorrectly pass P1 High-priority issues at the top of the work list team-engine Owned by Engine team triaged-engine Triaged by Engine team

Comments

@fluttergithubbot
Copy link
Contributor

The post-submit test builder Linux_pixel_7pro draw_atlas_perf__timeline_summary had a flaky ratio 2.04% 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/Linux_pixel_7pro%20draw_atlas_perf__timeline_summary/2163
Commit: 8c12ba8

Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_pixel_7pro%20draw_atlas_perf__timeline_summary/2163
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_pixel_7pro%20draw_atlas_perf__timeline_summary/2123

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

Please follow https://github.com/flutter/flutter/wiki/Reducing-Test-Flakiness#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-engine Owned by Engine team labels Apr 17, 2024
@jonahwilliams
Copy link
Member

I'm not sure if this is actually flaky or not. all I can see in the logs is that the test script failed to attach to the device. We've been doing some infra moves, I wonder if this was related?

@jonahwilliams jonahwilliams added P1 High-priority issues at the top of the work list triaged-engine Triaged by Engine team and removed P0 Critical issues such as a build break or regression labels Apr 22, 2024
@fluttergithubbot
Copy link
Contributor Author

[prod pool] flaky ratio for the past (up to) 100 commits between 2024-04-18 and 2024-04-23 is 0.00%. Flaky number: 0; total number: 97.

@fluttergithubbot
Copy link
Contributor Author

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

Copy link

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
c: flake Tests that sometimes, but not always, incorrectly pass P1 High-priority issues at the top of the work list team-engine Owned by Engine team triaged-engine Triaged by Engine team
Projects
None yet
Development

No branches or pull requests

2 participants