Age | Commit message (Collapse) | Author |
|
|
|
The lint is failing on CL, this appears to be due to the
RequiresApiTiramisuByDefault annotation.
Looks like the android.annotation.RequiresApi annotation
can be used on a package directly.
I've checked this on a CL and it appears to be WAI.
Let's try to submit this CL and check if the lint errors do
go away. Otherwise I'll revert back to using RequiresApi
on every class.
Test: lint works
Bug: 303836855
Relnote: N/A
Change-Id: Ied51bd506ec8a8ea59bbf63edd06423939df9a74
|
|
Auto-generated-cl: translation import
Change-Id: I6a95ee50a29f6e701d81787651ae875ce8df95d8
|
|
|
|
Auto-generated-cl: translation import
Change-Id: I351ab9817128179d9745dcb7c36460c2867aa85c
|
|
Auto-generated-cl: translation import
Change-Id: I20d14c700e94b3801f2ec9bf1d0153026a8591e3
|
|
Auto-generated-cl: translation import
Change-Id: I9e71e876dc31a38a5e054bab2401cc3b6833e2ac
|
|
Auto-generated-cl: translation import
Change-Id: I4638869a0132eb6321cccb69a013ace89efc00f1
|
|
Auto-generated-cl: translation import
Change-Id: Iaee36a306c936e1483472fccb3263ebd5555b5a5
|
|
Test: manual
Bug: 289076156
Relnote: N/A
Change-Id: I2f8b48405d1b15d157d50fb7c807a35c33f7266b
|
|
Auto-generated-cl: translation import
Change-Id: I2cf99032734b794fe94517c5a2fd590a739b3d2c
|
|
These are some of the slower tests, so seperate them from the rest to
increase changes of everything passing below runtime limits.
Bug: 292809502
Test: atest SafetyCenterFunctionalTestCases SafetyCenterSubpagesTestCases
Relnote: Split SafetyCenterSubpagesTestCases off of SafetyCenterFunctionalTestsCases in MTS
Change-Id: I6fea563b93a6edb1564f715f510702c0888f6b3f
|
|
This one is a bit trickier because tests rely on this in multiple ways:
- UI tests want to ensure that the data on the screen doesn't change,
however a refresh is triggered on page open and most tests set the data
manually rather than using the receiver to do so. The timeout could set
error on UI entries in the middle of the test, which isn't ideal. Worked
around this by setting the refresh timeout to the test timeout.
- Some existing tests were actively checking the behavior of that flag
and using the error listener as an easy way to check for timeouts.
I think it's a good thing to cleanup this flag regardless, as we ideally
want to have tests matching the production behavior, which wasn't the case
here (the flag was set to false in tests, but true in production code).
Bug: 289788052
Test: SafetyCenter tests
Relnote: N/A
Change-Id: I1f9dc8749d46f437c8dfbb98228ed1f042ee5821
|
|
Previously this test would only run as presubmit on changes in the test
directory.
Will monitor for flakiness but things seem fine with the latest changes
to the directory.
Relnote: n/a
Bug: 291893003
Test: treehugger on this CL
Change-Id: I72df704c30fb450d6e1fd89b35ea8a945c545ca9
|
|
|
|
Auto-generated-cl: translation import
Change-Id: Ie2bdb224538e4a0bbdc7cf06cee2cef384e6b51b
|
|
Auto-generated-cl: translation import
Change-Id: I318cf2638538451797add8870f9b2e22a23a1d26
|
|
|
|
Bug: 267476663
Test: atest SafetyCenterResourcesLibTests
Relnote: N/A
Change-Id: Ifae9d5a1edb404134f00116357e2925f52370f22
|
|
Bug: 260989965
Test: atest CtsSafetyCenterTestCases
Relnote: N/A
Change-Id: I2d85acad1940eca3acf3a64ba4abc27b7c62e8f9
|
|
Auto-generated-cl: translation import
Change-Id: I4636d0d32de2509724c3bbf66eda5969c55a58ea
|
|
Iff the device doesn't support Safety Center.
Previously the tests would crash if the resources APK is
not found while the device doesn't support SC.
Bug: 286532479
Test: atest CtsSafetyCenterTestCases &&
atest SafetyCenterFunctionalTestCases &&
atest SafetyCenterActivityFunctionalTestCases &&
atest SafetyCenterFunctionalMultiUsersTestCases
(with SC unsupported and resources APK not found)
Relnote: N/A
Change-Id: Ia10bb399748afa0aadcc771f447e89c80873ffac
|
|
into udc-mainline-prod
|
|
|
|
It's not really a Context anymore.
Bug: 283100177
Test: atest CtsSafetyCenterTestCases
Relnote: N/A
Change-Id: Iab9d28440f10c02a5e1a90fd0fbb95c53ab6b383
|
|
Auto-generated-cl: translation import
Change-Id: I02fed9b48e33dad00268d753b2315be8c824c5c1
|
|
Auto-generated-cl: translation import
Change-Id: I46f80f2dc4cb5ffc2a698374884475220121afe9
|
|
Stop making it implement ContextWrapper, that's error-prone
as it implies it has the Context from the resources APK as a base
when in fact the base is the context passed in; and methods are
overridden only partially.
Also increase test coverage.
Bug: 283100177
Test: atest CtsSafetyCenterTestCases
Relnote: N/A
Change-Id: I2925921de3de01633beacbbe713d46e9522f003b
|
|
Only cache the resources context, not every field.
Ideally it should implement ContextWrapper for the resources APK
context directly, I may follow up with another CL to do that (it's
a bit more risky and involved).
Also guard it by the API lock to make sure the resources context
is loaded at most once.
Bug: 283100177
Test: atest CtsSafetyCenterTestCases
Relnote: N/A
Change-Id: Ia54faa909105566fd5382c68b3e9046e1628267b
|
|
|
|
Auto-generated-cl: translation import
Change-Id: I02066063180c8dd3fb9ce2d41939e2c52773dd1c
|
|
Auto-generated-cl: translation import
Change-Id: I89761e00d1e7ed4f45361c41fe7acb23f5d92713
|
|
|
|
Auto-generated-cl: translation import
Change-Id: I83e3a9f3a360306ba810947f99318b52acdfc27a
|
|
Auto-generated-cl: translation import
Change-Id: I06e41a1b3db2cfcc91dd2a15e24f9bafcecf5605
|
|
Auto-generated-cl: translation import
Change-Id: If103dbcd43c1a31e4d8d388102ade92a01de5db1
|
|
Bug: 283100177
Test: atest SafetyCenterNotificationTest (on hsum)
Relnote: Fix crash in headless system user mode
Change-Id: Iec7e6bb36d00b23bbf8909058870b7f61eb7b2ec
|
|
Auto-generated-cl: translation import
Change-Id: I3a4661362bbe380adcda71230f168fbb724b1a4a
|
|
|
|
Auto-generated-cl: translation import
Change-Id: I763fe5f1f0d51c8d8b5abff9ffdb3fb466580260
|
|
Auto-generated-cl: translation import
Change-Id: I9a37f797ccc3572c929b3cc36c5315c9802bb3e1
|
|
The `@NonNullByDefault` annotation wasn't working as expected, using a
fork from another team instead. Also added it to the notifications
package where it was missing.
Running null analysis on the code spawned a few warnings, I tried to fix
most / all of them here. Some are benign (the checker has to understand
that a certain variable cannot be null), but some were genuine issues.
Bug: 267476663
Test: atest CtsSafetyCenterTestCases
Change-Id: I992ed765d02c1a7b0a39997ea3718e1de09d4986
|
|
|
|
|
|
Bug: 278674457
Test: manual
Change-Id: I9316d44060b742b51417470cc8c03e8dc623ebd9
|
|
Auto-generated-cl: translation import
Change-Id: I576f3121d81672af80d9eae7dde0a90dae98822b
|
|
Auto-generated-cl: translation import
Change-Id: I876395f19a28abf72bf4c7d31b41f7a84f8c0554
|
|
Using shared colors allows us to decide whether OEMs should be able to
overlay these colors or not.
Test: manual
Bug: 266052702
Change-Id: Ic052175e9bd1cc9805526178618299ead2b4a9da
|
|
|
|
|