In case the package manager is not yet started, retry saving the
profile up to 20 times to give it time. Should fix test flakiness.
Also addresses previous review comment.
Bug: 144048260
Bug: 139883463
Test: atest BootImageProfileTest
Change-Id: I12e101447d2a42fb0fcad7ad3427750c3ce89a79
Verify that the package manager constructor is in the profile.
Bug: 139883463
Test: atest BootImageProfileTest
Change-Id: I53350be972771c246c95f623eeb1289c59c9ba84
The frameworks jar was renamed to framework-minus-apex.jar.
Test: atest BootImageProfileTest
Bug: 139883463
Change-Id: I12d321f8458c584e3d262128d534e6f3c18b12a0
In the case where system server was not yet running, the invalid pid
would cause the test to fail instead of doing the 20 retry loop.
Fixed the logic to handle this case.
Presumably fixes test flakyness.
Bug: 143223380
Bug: 139883463
Test: atest ./tests/BootImageProfileTest/src/com/android/bootimageprofile/BootImageProfileTest.java
Change-Id: I4bac03e7f377058479f75daaa0d57608614bf329
Use these properties instead of system properties to get coverage.
Bug: 139883463
Test: atest BootImageProfileTest
Change-Id: I9275913ef109b5aaf0bdca6c07da8f102ecdc701
Keep trying to force profile saves until it's not empty. This handles
the case when the system server isn't started enough to save a profile
yet. This can be affected by boot time fluctuations if we don't wait.
Test: atest BootImageProfileTest
Bug: 139883463
Change-Id: I98b359412f919bd64c2cd2a5b7d6659d1cef113d
Test that the expected properties are set.
Test that saving the system server profile contains both the boot image
profile and system server profile.
The test requires root to run.
Bug: 139883463
Test: atest BootImageProfileTest
(cherry picked from commit f7849d916a)
Change-Id: Id7fa4ecc507864c2855da276025be076e5768df1
Merged-In: I6bb39337ba07be58b7dc2b314a8ee92154256f17