tree 6d6ea99201b18098137af1ce1119061c1aa7130a
parent 2ef7b3ec1d7d859bc1d1a08f2b2025754f75a15a
author Jing Ji <jji@google.com> 1564778655 -0700
committer Jing Ji <jji@google.com> 1565129921 -0700

Fix inconsistent OomAdjuster computation result

In case of cycle dependencies, while one of the process within
the cycle gets bound by mutliple other processes, the procState
result would be inconsistent across runs. Fix is to pick the
minimum one of the raw and current scores prior to scanning the
service/provider lists in case of cycles-reevaluation.

Bug: 138673927
Test: atest MockingOomAdjusterTests
      cts-tradefed run singleCommand cts-dev -m CtsAppTestCases \
      -t android.app.cts.ActivityManagerProcessStateTest

Change-Id: I8f33c12c1625da6f336d79e44e91158c84beb6ac