Fix incremental builds by applying sensible permissions
I055120a2ce9e0e19a50fcb5d1fa8f1fbf051312e included a classes.jar
file inside current/androidx/m2repository/androidx/media/media/1.6.0-beta02/media-1.6.0-beta02.aar
that had unusable permissions on the directories. When the classes.jar
is unzipped during a coverage build it created directories on disk
without the execute bit set, which cannot be deleted by rm -rf. The
files and directories were also all marked world writable.
Run chmod -R =rwX on all existing extractd directories to apply the
execute bit where necessary and reset the rest of the permissions
accorduing to the current umask.
Bug: 227470935
Test: none
Change-Id: Ic9c47bf28ceb828028d8f22313eb89e72e19b486
diff --git a/CleanSpec.mk b/CleanSpec.mk
index b84e1b6..e4055db 100644
--- a/CleanSpec.mk
+++ b/CleanSpec.mk
@@ -44,6 +44,8 @@
#$(call add-clean-step, find $(OUT_DIR) -type f -name "IGTalkSession*" -print0 | xargs -0 rm -f)
#$(call add-clean-step, rm -rf $(PRODUCT_OUT)/data/*)
+$(call add-clean-step, chmod -R =rwX $(OUT_DIR)/target/common/obj/APPS/*_intermediates/jacoco/work/classes-to-instrument/classes)
+
# ************************************************
# NEWER CLEAN STEPS MUST BE AT THE END OF THE LIST
# ************************************************