Flaky build failure in MergeResources task [206674992]

Fixed

Bug

Status Update

No update yet.

Description

ku...@gmail.com

created issue #1

Nov 16, 2021 11:23PM

On CI builds we are seeing the following build failure happen occasionally during an incremental build. For example we do a build, then apply a change from a git commit, and build again.

We have enabled the following two properties for making the mergeResources task relocatable which could be the reason from looking at the stacktrace:

android.experimental.enableSourceSetPathsMap=true
android.experimental.cacheCompileLibResources=true

The app module also uses custom res source set locations in case that is relevant:

android.sourceSets { main.res.srcDirs = [ 'src/main/res/foo', 'src/main/res/bar' ] }

Stacktrace:

Task :app:mergeReleaseResources
java.lang.IllegalArgumentException: Unable to locate resourceFile (/.../app/build/intermediates/merged-not-compiled-resources/release/interpolator/mtrl_fast_out_slow_in.xml) in source-sets.
	at com.android.ide.common.resources.RelativeResourceUtils.getRelativeSourceSetPath(RelativeResourceUtils.kt:46)
	at com.android.ide.common.resources.MergedResourceWriter.getSourceFilePath(MergedResourceWriter.java:333)
	at com.android.ide.common.resources.MergedResourceWriter.removeOutFile(MergedResourceWriter.java:755)
	at com.android.ide.common.resources.MergedResourceWriter.removeFileFromNotCompiledOutputDir(MergedResourceWriter.java:723)
	at com.android.ide.common.resources.MergedResourceWriter.removeOutFile(MergedResourceWriter.java:741)
	at com.android.ide.common.resources.MergedResourceWriter.removeItem(MergedResourceWriter.java:448)
	at com.android.ide.common.resources.MergedResourceWriter.removeItem(MergedResourceWriter.java:71)
	at com.android.ide.common.resources.DataMerger.mergeData(DataMerger.java:276)
	at com.android.ide.common.resources.ResourceMerger.mergeData(ResourceMerger.java:385)
	at com.android.build.gradle.tasks.MergeResources.doTaskAction(MergeResources.java:497)
	at com.android.build.gradle.internal.tasks.NewIncrementalTask$taskAction$$inlined$recordTaskAction$1.invoke(BaseTask.kt:66)
	at com.android.build.gradle.internal.tasks.Blocks.recordSpan(Blocks.java:51)
	at com.android.build.gradle.internal.tasks.NewIncrementalTask.taskAction(NewIncrementalTask.kt:45)

Version of Gradle Plugin: 7.0.0

Version of Gradle: Gradle 7.2

Version of Java: 11

OS: centOS

Comments

gh...@google.com <gh...@google.com> Nov 17, 2021 09:05PM

Assigned to an...@google.com.

je...@google.com <je...@google.com> Nov 22, 2021 05:54PM

Reassigned to cm...@google.com.

ku...@gmail.com <ku...@gmail.com> #2Feb 26, 2022 12:38AM

Will be this fix also part of 4.2 please?

ga...@google.com <ga...@google.com> #3Aug 23, 2022 11:32AM

for the "out" bundle issue, this seems indeed an issue. for the second one reported adding "debugUpdateAPKArtifact" to the path, this WAI as there can more more than one transformer and we need to automatically separate them so they do not use the same output folder. for #3, I will look at it but it might be difficult to change it at this time.

Message last modified on Aug 23, 2022 11:34AM

inc_res.zip

847 KB

Download

lu...@google.com <lu...@google.com> Aug 23, 2022 11:35AM

Accepted by lu...@google.com.

lu...@google.com <lu...@google.com> #4Aug 23, 2022 01:58PM

I understand that if there is more transformer is necessary to make every folder different, but there is the main problem, that the final one (last transform) is inside of the intermediate folder. The last transformation should end in the standard location, right? Maybe also with the default name not?

lu...@google.com <lu...@google.com> #5Aug 23, 2022 02:37PM

Hello, this is a P1 S1 issue for a while now, and it's blocking us from upgrading to AGP 4.2 and further. What's the current status? And do you have plans to backport it to 4.2.x?

lu...@google.com <lu...@google.com> Aug 23, 2022 04:39PM

Marked as fixed.

pa...@gmail.com <pa...@gmail.com> #6Mar 7, 2023 03:40PM

no we don't have a plan to backport this. why is this blocking you from upgrading ?

kh...@gmail.com <kh...@gmail.com> #7Apr 4, 2023 06:57AM

Comment has been deleted.

Message last modified on Apr 4, 2023 01:42PM

sa...@peilicke.de <sa...@peilicke.de> #8May 25, 2023 07:51AM

I commented on the merge request but to summarize :

you can set your signing tasks output folder to wherever you need to be :

artifacts.use(target.tasks.signedApkTaskProvider(this)).configure { signedDirProperty.set(File("/path/to/where/you/want/your/signed/files")) }

if you don't set it, then we will set a directory automatically.

lu...@google.com <lu...@google.com> #9May 25, 2023 01:32PM

Thanks, Jerome!