这是indexloc提供的服务,不要输入任何密码
Skip to content

Fix flaky complex_layout_scroll_perf__memory & flutter_gallery__memory_nav #150368

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

Merged
merged 4 commits into from
Jun 17, 2024

Conversation

jtmcdole
Copy link
Member

Initial tap is missing sometimes; either its never delivered or it is
delivered before gesture controller is hooked up.

1: Update MemoryTest to have option requiresTapToStart guarding the
new paths
2: Update the two perf tests that appear to be flaky to output when
TAPPED is received
3: Update the MemoryTest to keep tapping while waiting for TAPPED

Tested on devicelab:

  • setting iterations=1
  • removing the timeout before READY
  • running tests in a while loop

Before this change, you could get the test to hang often. After this
change you'll see "tapping device... [x]" where x is the counter.

Fixes #150096

jtmcdole and others added 4 commits June 14, 2024 16:25
Initial tap is missing sometimes; either its never delivered or it is
delivered before gesture controller is hooked up.

1: Update the two perf tests to output when TAPPED is received
2: Update the MemoryTest to keep tapping while waiting for TAPPED

Tested on devicelab:
* setting iterations=1
* removing the timeout before READY
* running tests in a while loop

Before this change, you could get the test to hang often. After this
change you'll see "tapping device... [x]" where x is the counter.

Fixes flutter#150096
Co-authored-by: gaaclarke <30870216+gaaclarke@users.noreply.github.com>
- Wait out any errant taps (~200ms)
- Update i->tapCount
Initial tap is missing sometimes; either its never delivered or it is
delivered before gesture controller is hooked up.

1: Update MemoryTest to have option `requiresTapToStart` guarding the
   new paths
2: Update the two perf tests that appear to be flaky to output when
   TAPPED is received
3: Update the MemoryTest to keep tapping while waiting for TAPPED

Tested on devicelab:
* setting iterations=1
* removing the timeout before READY
* running tests in a while loop

Before this change, you could get the test to hang often. After this
change you'll see "tapping device... [x]" where x is the counter.

Fixes flutter#150096
@jtmcdole jtmcdole requested a review from gaaclarke June 17, 2024 16:34
@github-actions github-actions bot added the f: scrolling Viewports, list views, slivers, etc. label Jun 17, 2024
@jtmcdole jtmcdole added autosubmit Merge PR when tree becomes green via auto submit App fyi-infra For the attention of Infrastructure team and removed f: scrolling Viewports, list views, slivers, etc. labels Jun 17, 2024
@gaaclarke
Copy link
Member

note: the previous PR that fixed this was reverted: #150287

@jtmcdole
Copy link
Member Author

note: the previous PR that fixed this was reverted: #150287

I should have noted that. Was following the hygiene document and trying not to use "reland":

When you later revert the revert, just land the PR afresh with the original commit message, possibly updated with the information since collected, and include a link to the original PR and to the revert PR so that people can follow the breadcrumbs later.

The revert was here #150293

Copy link
Member

@gaaclarke gaaclarke left a comment

Choose a reason for hiding this comment

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

Code looks good to me. It still bothers me we have to do this. I feel like there has to be an appropriate proxy or callback for this. Like, is it possible that a frame has been rendered but the gesture recognizers have not been installed?

@auto-submit auto-submit bot merged commit e80bbd9 into flutter:master Jun 17, 2024
138 checks passed
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Jun 17, 2024
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Jun 17, 2024
@jtmcdole jtmcdole deleted the fixFlakyMemPerf2 branch June 17, 2024 18:28
auto-submit bot pushed a commit to flutter/packages that referenced this pull request Jun 17, 2024
flutter/flutter@5187cab...ccf3abe

2024-06-17 engine-flutter-autoroll@skia.org Roll Flutter Engine from 2218a4566765 to 5989f0215fed (9 revisions) (flutter/flutter#150373)
2024-06-17 mit@google.com Update API docs footer (flutter/flutter#150347)
2024-06-17 katelovett@google.com Update old wiki links (flutter/flutter#149544)
2024-06-17 codefu@google.com Fix flaky complex_layout_scroll_perf__memory  & flutter_gallery__memory_nav (flutter/flutter#150368)
2024-06-17 engine-flutter-autoroll@skia.org Roll Packages from dd04ab1 to 711b4ac (3 revisions) (flutter/flutter#150359)
2024-06-17 engine-flutter-autoroll@skia.org Roll Flutter Engine from 9779c273aac3 to 2218a4566765 (3 revisions) (flutter/flutter#150298)

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 rmistry@google.com,stuartmorgan@google.com 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
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Aug 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
autosubmit Merge PR when tree becomes green via auto submit App fyi-infra For the attention of Infrastructure team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Linux_mokey complex_layout_scroll_perf__memory is 2.44% flaky
2 participants