Skip to content

Marks Linux_pixel_7pro new_gallery__transition_perf to be flaky #174106

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

fluttergithubbot
Copy link
Contributor

Issue link: #174105

@fluttergithubbot fluttergithubbot added the team-engine Owned by Engine team label Aug 20, 2025
@flutter-dashboard flutter-dashboard bot added c: flake Tests that sometimes, but not always, incorrectly pass c: tech-debt Technical debt, code quality, testing, etc. labels Aug 20, 2025
@github-actions github-actions bot removed c: tech-debt Technical debt, code quality, testing, etc. team-engine Owned by Engine team labels Aug 20, 2025
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a 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 marks the Linux_pixel_7pro new_gallery__transition_perf test as flaky. The change is correct in principle, but the comment format for marking the test as flaky does not follow the documented convention in docs/infra/Reducing-Test-Flakiness.md. I've added a comment with a suggestion to align with the repository's guidelines.

@@ -3190,6 +3190,7 @@ targets:

# Pixel 7 Pro, Skia
- name: Linux_pixel_7pro new_gallery__transition_perf
bringup: true # Flaky https://github.com/flutter/flutter/issues/174105
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The comment format for marking a test as flaky doesn't follow the documented convention. According to docs/infra/Reducing-Test-Flakiness.md (line 34), the comment should be on a separate line above bringup: true and use the format # TODO(username): github issue url. Please update the comment to match this format, replacing <github_username> with the appropriate username.

    # TODO(<github_username>): https://github.com/flutter/flutter/issues/174105
    bringup: true

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c: flake Tests that sometimes, but not always, incorrectly pass
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant