summaryrefslogtreecommitdiff
path: root/test/MultiDexModifiedSecondary/Second.java
diff options
context:
space:
mode:
authorAlex Light <allight@google.com>2020-10-06 15:26:58 -0700
committerTreehugger Robot <treehugger-gerrit@google.com>2020-10-08 15:28:03 +0000
commit2734999f931a0e9082df7ae492dbfde668cd38d0 (patch)
tree28d34c9254f21b878299bf40e4e231b3ae621e0f /test/MultiDexModifiedSecondary/Second.java
parent5409408a41045c7f178e362311eb51dab992d6db (diff)
Fallback to using ANDROID_HOST_OUT env-var in gtests
When running gtests using external runners in conjunction with certain runners the gtest can believe that it is being run from a directory other than ANDROID_HOST_OUT. Instead of aborting this change makes the gtest simply accept the env-var and use it instead of trying to determine it based on the executable's path. Test: manual, VSCode Change-Id: I1ae7bbc58bea1813683d3180c9ee93be21f21df5
Diffstat (limited to 'test/MultiDexModifiedSecondary/Second.java')
0 files changed, 0 insertions, 0 deletions