Test is failing on a subset of devices with a memory leak in an activity.
This is not repoing on other devices so could be a problem with the setup
rather than the code.
Bug: 190618549
Test: Local
Change-Id: I9c6a56432d1b1f59c337bf34e7b8c26befeb2d7d
Widget parts of ViewInflationDuringSwipeUp are failing on some devices,
looks like a test architecture problem, not a code failing problem.
Bug: 190729479
Test: Ran remaining tests
Change-Id: I7598f381053f7136b2fcd861ec73d2fda239bb8d
Disable chips by default as they are not plan of record for launch.
Bug: 141579810
Test: Local and ran test
Change-Id: Iae270c6ac4bbec4f7c29b1137cf926383443e85e
This reverts commit 395c58d303.
Reason for revert: The bug was fixed
Bug: 187899876
Change-Id: I73f93f5fb1ec0ab0352ba174aabbaf6935dd9fc4
Test: presubmit
This reverts commit 17ba630cd9.
Reason for revert: For unknown reasons, the problem had fixed itself
Change-Id: Ifdf884a4ca0e3cd96d85da2725216fd34bfdcbe0
Live tile changes certain assumptions we have for tests, for example
- Launcher will not be in the resumed state after swiping up to Overview
Also, disable live tile for 3rd party launcher for now
Test: presubmit
Fixes: 169694902
Change-Id: Ifd466db0354f59290c4f66a0a2ad4c82f1169f29
Apparently, we can't generally expect that flinging to and
fro will return Overview to the original task, especially
if the device performance is low.
Now starting the expected task explicitly.
Test: presubmit
Bug: 182794819
Change-Id: Ia2931f4f3005c46dd72990c247a90f9010b9b8d5
I will use the newly created LauncherAppWidgetProviderInfoTest in a follow-up CL to add tests for the newly added widget sizing APIs.
Test: Automatic: Ran all robolectric tests in launcher3,
Manual: Added a widget, edited the widget, removed the widget
Bug: 179807199
Change-Id: I540b2dbe284c6eb5aa2466a1d13a9581ee59425b
Presumably, we currently have flakes when immediately
after orientation change, we check for the presence of certain
views, and they are still not present.
Test: presubmit
Bug: 181057446
Change-Id: I6dbcb757a47c19728d4096283da6710f6dd5aa02
It wasn't updated for a while,
creates a false impression that the failure
is already tracked, and hopefully soon
will be replaced by new clustering.
Test: presubmit
Bug: 161478674
Change-Id: Icc3716c1f534867d5e4b21d18c9cede273da8704
I suspect it may wait for a period of time less than
the specified one, causing flakes.
Test: presubmit
Bug: 177318681
Change-Id: I0be8790c6ee9a5831767fe83c36054ed5a84f8d7
Test: manual, presubmit on the source branch
x20/teams/android-launcher/merge/ub-launcher3-master_master_6852432.html
Change-Id: I91066d6c55e88355a10a61281ad0d9b38b43f166
Test: manual, presubmit on the source branch
x20/teams/android-launcher/merge/ub-launcher3-master_master_6767682.html
Change-Id: I5e9c73a7ac3033fe82006c4bd72824f56b8988f8
Predictions are loaded and managed by Launcher model and follow
the model lifecycle. They are then bound to the callback which
handles the UI
Bug: 160748731
Change-Id: I4a3ea0698d80fafe94afb4ce66ffa7f4a6a91c68
It flakes when one of the tests starts calculator while there zero
activities in the system.
Bug: 143488140
Change-Id: Id9d350f0de8a83eb50e35e9efa4226b8d45ca641
It's a flake.
It was likely caused by enabling fallback tests, and we don't know
what's leaked and why.
Bug: 143488140
Change-Id: I0d0c88ac9b0de316861f16ba023a596c1f39cde4
vadimt