diff options
| author | 2022-02-02 15:35:10 +0000 | |
|---|---|---|
| committer | 2022-02-02 17:26:14 +0000 | |
| commit | b4df138d00c3c9a704615ec163a20b8236692aaf (patch) | |
| tree | 641d73455d939c23f6ac8917a043e4cd81a00b90 /test/MultiDex/Main.java | |
| parent | a8ee39d086dd61e0d27c613725e40f0d5787bc37 (diff) | |
Fix broken test
The assertion here is just wrong. In setup we install a new ART APEX
and reboot, which will recompile both Zygote and System Server
artifacts.
Then the test marks a different APEX as updated and triggers
recompilation, which should only affect System Server artifacts,
precisely because --compilation-os-mode no longer does a
force-compile.
This new version is exactly what Jiakai said I should do
(https://r.android.com/c/platform/art/+/1964960/1..4//COMMIT_MSG#b21,
https://r.android.com/1964844), but somehow I managed to convince
myself to do the wrong thing instead.
Bug: 217446385
Bug: 211458160
Test: atest OdrefreshHostTest#verifyCompilationOsMode
Change-Id: I10cac92c6abf4eead1f25a85a15de271dccfd78c
Diffstat (limited to 'test/MultiDex/Main.java')
0 files changed, 0 insertions, 0 deletions