Added strict_mode: false to android.bp for the robolectric tests
The robolectric tests were failing because isRobolecticTest() references
android.os.Build which is injected as part of the Robolectric environment,
unforatunately, after the Rule is instantiated, which causes the test to
fail. Turning off strict_mode in Android.bp works around this.
Bug: 334089788
Flag: TEST_ONLY
Test: tested manually with atest
Change-Id: Iac7486e82a801600a84d4f17854f97cc3bedd99b
diff --git a/packages/SystemUI/Android.bp b/packages/SystemUI/Android.bp
index ac680a9..e940674 100644
--- a/packages/SystemUI/Android.bp
+++ b/packages/SystemUI/Android.bp
@@ -752,6 +752,7 @@
plugins: [
"dagger2-compiler",
],
+ strict_mode: false,
}
// in-place tests which use Robolectric in the tests directory
@@ -771,7 +772,6 @@
],
static_libs: [
"RoboTestLibraries",
- "mockito-kotlin2",
],
libs: [
"android.test.runner",
@@ -787,6 +787,7 @@
plugins: [
"dagger2-compiler",
],
+ strict_mode: false,
}
android_ravenwood_test {