summaryrefslogtreecommitdiff
path: root/test/MultiDexModifiedSecondary
diff options
context:
space:
mode:
authorHans Boehm <hboehm@google.com>2020-04-28 15:11:21 -0700
committerLokesh Gidra <lokeshgidra@google.com>2020-04-29 17:28:46 +0000
commit2a84650a73a0a5fb3d5311539342a02bcf1321d3 (patch)
treed87062368efa3e637724e27f0b5db089527a0533 /test/MultiDexModifiedSecondary
parentb6ea8bbab6173b9fc0a5496417842a63a25986fd (diff)
Make tests robust against GCs failing early
044-proxy, 064-field-access, 080-oom-throw, and 617-clinit-oome all intentionally run out of memory, and then try to run a test with a full heap. In the presence of aosp/1286274, this can fail if we initially had some empty space in the heap. A GC may recover < 1% of space, in which case we return OOME. But later allocations may still succeed. The fix is to make sure there is no empty space in the heap when we start. If we end up performing a forced GC, the heap was completely full. Since no memory is dropped during this process, the heap will still be full when we finish. Test: testrunner.py --host -t 044-proxy & Test: testrunner.py --host -t 080-oom-throw Change-Id: I10e3f77cd16d25af96751d039e2e498e1cb43315
Diffstat (limited to 'test/MultiDexModifiedSecondary')
0 files changed, 0 insertions, 0 deletions