Closed plastiv closed 4 years ago
I don't believe this is actually an overlapping output based on the output path. But rather the logcat file being change outside of the time Gradle expects it to be.
What versions of adb / composer / this plugin / Gradle / Android Gradle plugin produced this? I'll try to repro on my end
My environment is:
And I've currently applied composer plugin to 2 submodules:
rootprojectdir
├── main
│ ├── build.gradle
├── storage
│ ├── build.gradle
And try to run composer for both of them by executing ./gradlew testDebugComposer
from root dir.
Composer config
apply plugin: 'com.trevjonez.composer'
composer {
instrumentationArgument('disableAnalytics', 'true') // google reports amount of test runs by default
if (project.hasProperty('ORCHESTRATOR')) {
withOrchestrator true
instrumentationArgument('clearPackageData', 'true') // orchestrator param
}
}
dependencies {
if (project.hasProperty('ORCHESTRATOR')) {
androidTestUtil libraries.testOrchestrator
}
composer libraries.composer
}
NOTE: if I don't apply plugin: 'com.trevjonez.composer'
to one of the modules the warning is gone.
thank you for such a thorough response. i'll see if I can dig into this over the holidays. Perhaps the fix here might also fix #26 , smells maybe related.
@plastiv I pushed rc04 which I believe should correct this issue. The thinking is that adb was left running in the background long enough to cause issues. the change today forcefully kills the spawned process during the rx disposal.
should be fully resolved in rc05 based on feedback from others experiencing this issue periodically.
if not feel free to let me know here and we can reopen the investigation.
ComposerTask
is marked as @CacheableTask and so is participating in gradle cache lifecycle but is not cooperative.We are observing next crashes on our CI pipelines
Running with
org.gradle.caching.debug=true
results in next warnings