Apex_available check failure reveals dependency
When the check for apex_available has failed, the build system now shows
the module that brought the unavailable module into the APEX.
Bug: 151051671
Test: m
Merged-In: Id1a3fda67fe56fdc2dc90ec800d10689415de4d6
(cherry picked from commit 7bd9444b0fb928b7c05d50376f22e37a961bb499)
Change-Id: Id1a3fda67fe56fdc2dc90ec800d10689415de4d6
diff --git a/apex/apex_test.go b/apex/apex_test.go
index 2b13197..7b842da 100644
--- a/apex/apex_test.go
+++ b/apex/apex_test.go
@@ -3345,7 +3345,7 @@
func TestApexPropertiesShouldBeDefaultable(t *testing.T) {
// libfoo's apex_available comes from cc_defaults
- testApexError(t, `"myapex" .*: requires "libfoo" that is not available for the APEX`, `
+ testApexError(t, `"myapex" .*: "myapex" requires "libfoo" that is not available for the APEX`, `
apex {
name: "myapex",
key: "myapex.key",