Don't use the default boot image location with non-default bootclasspath
Some unit tests are using a non-default bootclasspath. In such cases,
the runtime cannot use the default boot image location anyway.
Before this change, during those tests, the runtime attempted to use the
default boot image location and then rejected it. This workflow worked
for a long time. However, it no longer works since aosp/2458432 because
that CL introduced some logic that infers the default boot image
location based on environment variables, which may not exist in some
chroot environment.
After this change, the runtime doesn't attempt to use the default boot
image location at all.
This fixes the LUCI breakage caused by aosp/2458432.
Bug: 269230245
Test: Presubmit
Change-Id: Iecd9b7d05fa91fd96eee5072ca5797c08c36a16e
3 files changed