mirror of
https://github.com/flutter/flutter.git
synced 2025-06-03 00:51:18 +00:00
![]() Relands https://github.com/flutter/flutter/pull/150808 The original version of the pr [accidentally deleted the back button](https://github.com/flutter/flutter/pull/150808#discussion_r1655444210), which didn't block the app building but made the test hang because it couldn't back out of the demo pages. Repro-ed the failure, and then tested that ``` new_gallery_opengles_impeller__transition_perf new_gallery__transition_perf new_gallery_impeller_old_zoom__transition_perf new_gallery__crane_perf new_gallery_impeller__transition_perf ``` All pass on my pixel 7 pro, with ` dart bin/test_runner.dart test -t <test>`, after re-adding the mistakenly deleted content. Did not test on an iOS device (I don't have one), but those tests were failing for the same reason from what I can tell: ``` > reply@study [2024-06-26 12:49:21.884543] [STDOUT] stdout: [ ] scrolling to demo [2024-06-26 12:49:22.412479] [STDOUT] stdout: [ +527 ms] tapping demo [2024-06-26 12:49:28.075978] [STDOUT] stderr: [+5663 ms] VMServiceFlutterDriver: tap message is taking a long time to complete... ``` Which is the same error, and which makes sense - they got stuck because they couldn't back out of the page. Sorry for the churn ð |
||
---|---|---|
.. | ||
a11y_assessments | ||
automated_tests | ||
benchmarks | ||
bots | ||
conductor | ||
customer_testing | ||
devicelab | ||
docs | ||
forbidden_from_release_tests | ||
integration_tests | ||
manual_tests | ||
missing_dependency_tests | ||
snippets | ||
tools | ||
tracing_tests | ||
analysis_options.yaml | ||
README.md |
This directory contains tools and resources that the Flutter team uses during the development of the framework. The tools in this directory should not be necessary for developing Flutter applications, though of course, they may be interesting if you are curious.
The tests in this directory are run in the framework_tests_misc-*
shards.