AGP should concatenate multiple .ec files when using Test Orchestrator [72758547]

Fixed

Bug

[AOSP] assigned

Status Update

No update yet.

Description

ju...@gmail.com

created issue #1

Feb 1, 2018 02:13PM

Hi,

Enabling test orchestration causes incorrect coverage report statistics. Only the last run test will have coverage data correctly reported, all other test coverage data is lost when looking at the report.

I have attached a vanilla app created by android studio that has coverage enabled, test orchestrator enabled, and two tests that test two methods in the main activity.

Running the generated task 'createDebugAndroidTestCoverageReport' and checking the report will show only the last executed test has correct coverage data.

Libraries used: Espresso:3.0.1, Runner:1.0.1

What steps will reproduce the problem?
1. Create a vanilla app from the android studio prompt.
2. Enable test coverage in the debug buildtype (testCoverageEnabled = true)
2b. Enable test orchestration in testOptions (execution 'ANDROID_TEST_ORCHESTRATOR')
3. Create two test methods in the main activity (they can be static)
4. Create two tests in androidTest to test those methods.
5. Run the 'createDebugAndroidTestCoverageReport'
6. Open the report index: /build/reports/coverage/index.html
7. Navigate to the MainActivity and check the coverage for the two test methods.

EXPECTED: Both test methods are reported as covered.
ACTUAL: Only the last run test subject (method under test) has coverage reported.

How are you running your tests (via Android Studio, Gradle, adb, etc.)?
Gradle / Android Studio Gradle Projects Window using the 'createDebugAndroidTestCoverageReport'

What is the expected output? What do you see instead?
Code Coverage reports all methods have coverage.

OrchestratorCoverage.zip

26 MB

Download

Comments

gg...@google.com <gg...@google.com> Feb 5, 2018 02:55PM

Assigned to gg...@google.com.

gg...@google.com <gg...@google.com> #2Feb 6, 2018 06:04AM

First of all thanks for this detailed issue.

This issue had been investigated thoroughly when it was first reported internally. The surprising detail in this report is that the issue is not reproducible before 1.7. I will look into this.

The main problem with POBox is the fact that it is deprecated. Since 2021 Sony has been shipping new Xperia devices with Gboard pre-installed. Although we are aware that there is still a considerable amount of users still using POBox, the described behavior is caused by POBox's noncompliant behavior with InputConnection and InputMethodManager documentation. However, this is understandable since TextView implementation was also not respecting the behavior that is expected from Editors.

Ultimately we have decided to enforce the documented behavior with specifically regards to when editors should call InputMethodManager.updateSelection. Also, although unconfirmed, there were traces of possible custom code being included in Sony OEM images that changed how InputMethodManager was notified from TextView. If POBox also depended on something like this, it would be impossible for Compose code to replicate the same unknown behavior.

[Deleted User] <[Deleted User]> #3Feb 21, 2018 07:59PM

If the investigation takes time, would it be possible to revert the surrounding implementation to 1.6.x equivalent?

Or is that option not available?

Even if the root cause is POBox, from the perspective of the app's customers, it looks like an app bug, so this issue is a blocker against updating Jetpack Compose.

ay...@blink22.com <ay...@blink22.com> #4Feb 22, 2018 11:24AM

Just to be sure, it is dangerous to replace Compose TextField with Android View EditText as a workaround for this issue.

Compose 1.7 has a bug that causes ANR when the focus is on EditText. https://issuetracker.google.com/issues/369354336

Another View-related bug in Compose 1.7 is that an Android View is focused by calling FocusManager.clearFocus(). https://issuetracker.google.com/issues/374031296

Perhaps there is a lack of testing of Compose 1.7 in combination with Android View. There is also a possibility that there are other fatal bugs related to View.

In other words, the only options for apps targeting the Japanese market that require POBox support are to continue using Compose 1.6 or to use EditText in combination with various workarounds.

be...@gmail.com <be...@gmail.com> #5Feb 25, 2018 06:47PM

Project: platform/frameworks/support
Branch: androidx-main
Author: Halil Ozercan <halilibo@google.com>
Link: https://android-review.googlesource.com/3317256

Fix POBox keyboard issue

Expand for full commit details

Fix POBox keyboard issue 
 
Fix: 373743376 
Fix: 329209241 
Test: NullableInputConnectionWrapperTest 
Change-Id: I94e0e598274fb88b255f977f9fbd50dfbbb1ecb1

Files:

M compose/ui/ui/src/androidInstrumentedTest/kotlin/androidx/compose/ui/text/input/NullableInputConnectionWrapperTest.kt
M compose/ui/ui/src/androidMain/kotlin/androidx/compose/ui/text/input/NullableInputConnectionWrapper.android.kt

Hash: 57f58c4b80d5d8470b2aca325dfdcd55f235231e
Date: Thu Oct 24 01:25:20 2024

so...@gmail.com <so...@gmail.com> #6Feb 27, 2018 03:20PM

Many thanks again for this report. Especially for giving us a huge clue in terms of what could be going wrong. The fix is now merged and I will ask for a cherry-pick into a stable release.

ga...@google.com <ga...@google.com> #7Feb 27, 2018 03:31PM

Thank you for fixing the issue, I confirmed the fix was released in version 1.8.0-alpha05.
Do you have any concrete plan to cherry-pick the fix into current stable version (1.7.x)? We are currently waiting it.

nk...@google.com <nk...@google.com> #8Feb 27, 2018 07:19PM

Yes, this fix is planned to be included in a future 1.7.x release.

ay...@blink22.com <ay...@blink22.com> #9Mar 20, 2018 01:03PM

Thanks for the fix. Sorry to follow up on this. is it possible for you to share specific release version/date for the stable version? We are waiting on this to decide on our direction.

nk...@google.com <nk...@google.com> Mar 20, 2018 05:23PM

Reassigned to nk...@google.com.

ju...@gmail.com <ju...@gmail.com> #10Mar 28, 2018 01:01AM

Hi is there any update to this issue?

nk...@google.com <nk...@google.com> #11Mar 28, 2018 05:50AM

Yes, we're working on resolving this issue for next release.

nk...@google.com <nk...@google.com> #12Mar 28, 2018 07:01PM

Reassigned to ga...@google.com.

I added the ability for Orchestrator to generate a coverage file per test. Reassigning this bug to the Studio/Gradle team to utilize this feature when pulling the coverage files from the device.

[Deleted User] <[Deleted User]> #13Apr 15, 2018 09:57AM

If I understand correctly, the fix will be included in the next gradle plugin version.
Is that right?

nk...@google.com <nk...@google.com> #14Apr 16, 2018 05:46PM

This fix will be included in the next release of Orchestrator for sure.

The Android Studio/Gradle team and the Firebase team will need to adopt this fix in order to make the integration with their respective tools work. I will leave it up to them to provide an estimate on when that's going to be ready.

ga...@google.com <ga...@google.com> May 1, 2018 05:11PM

Accepted by ga...@google.com.

[Deleted User] <[Deleted User]> #15May 7, 2018 10:48PM

Using version 1.0.2 of the orchestrator crashes every time if code coverage is enabled:
Sample

https://github.com/suarezjulian/unified-code-coverage-android

./gradlew jacocoTestReport
Starting a Gradle Daemon, 1 incompatible Daemon could not be reused, use --status for details
Parallel execution is an incubating feature.
Starting 0 tests on Pixel 2 - 8.1.0
Tests on Pixel 2 - 8.1.0 failed: Instrumentation run failed due to 'Process crashed.'

com.android.builder.testing.ConnectedDevice > No tests found.[Pixel 2 - 8.1.0] FAILED
No tests found. This usually means that your test classes are not in the form that your test runner expects (e.g. don't inherit from TestCase or lack @Test annotations).

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:connectedDebugAndroidTest'.
> There were failing tests. See the report at: {}/unified-code-coverage-android/app/build/reports/androidTests/connected/index.html

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at

https://help.gradle.org

BUILD FAILED in 25s

ga...@google.com <ga...@google.com> #16May 8, 2018 09:24AM

Test orchestrator 1.0.2 does not work yet with the Android Gradle plugin. Fix is underway, and I will update the bug once it has been merged.

ga...@google.com <ga...@google.com> #17May 18, 2018 08:01AM

Marked as fixed.

The fix should be release in Android Gradle plugin 3.2.0-alpha17.

Fixed in ag/Ib7377ad308b266fb79c753a859c4bf75d43e029f

co...@gmail.com <co...@gmail.com> #18May 23, 2018 01:59PM

It seems that in the AndroidTestOrchestrator.java the method:

---------------
static String addTestCoverageSupport(Bundle bundle, String str) {
if (!shouldRunCoverage(bundle) || !runsInIsolatedMode(bundle)) {
return null;
}
String string = bundle.getString("coverageFilePath");
if (string == null || string.isEmpty()) {
throw new IllegalStateException(String.format("The coverage path [%s] is either null or empty", new Object[]{string}));
} else if (bundle.getString("coverageFile") == null) {
return new StringBuilder((String.valueOf(string).length() + 3) + String.valueOf(str).length()).append(string).append(str).append(".ec").toString();
} else {
throw new IllegalStateException(String.format("Can't use a custom coverage file name [-e %s %s] when running through orchestrator in isolated mode. Since the generated coverage files will overwrite each other. Please consider using [%s] instead.", new Object[]{"coverageFile", bundle.getString("coverageFile"), "coverageFilePath"}));
}
}
---------------

Throws an ISE exception if it does not find the coverageFilePath. Is this caused by the fact that no such parameter is specified when executing:

---------------
V/ddms: execute: running CLASSPATH=$(pm path android.support.test.services) app_process / android.support.test.services.shellexecutor.ShellMain am instrument -r -w -e targetInstrumentation com.jpmorgan.am.ipbonline.instr.test/android.support.test.runner.AndroidJUnitRunner -e coverageFile /data/data/com.jpmorgan.am.ipbonline.instr/

coverage.ec -e coverage true -e clearPackageData true android.support.test.orchestrator/android.support.test.orchestrator.AndroidTestOrchestrator
---------------

I just want to confirm if this is the cause of the process crash 'Instrumentation run failed due to 'Process crashed'.'

sl...@google.com <sl...@google.com> #19May 23, 2018 07:10PM

That's correct, but we already fixed that behaviour in the alpha2 release (androidx.test:runner:1.1.0-alpha1) to be backwards compatible.

is...@gmail.com <is...@gmail.com> #20Jul 1, 2018 01:43PM

Thanks to Google team, JaCoCo is now working with Orchestrator perfectly. (N.B used: gradle: 3.2.0-alpha17, test:runner: 1.0.2)

do...@gmail.com <do...@gmail.com> #21Jul 27, 2018 06:31PM

I had an android project that used orchestrator 1.0.1 and it worked fine in the test case. However in the code coverage it did not generate the right result.
So I changed the orchestrator to 1.0.2 (did not make any changes in the test cases). Gradle can sync but when I tried to generate the report with "createDebugAndroidTestCoverageReport" task, it said "com.android.builder.testing.ConnectedDevice > No tests found"
So in short, if I used an older version of orchestrator, the report returned wrong result
If i used a new version of orchestrator, it has error.

Does anyone have the similar issue? Is that orchestrator 1.0.2 still a little bit buggy or I missed something?

Thanks.

ga...@google.com <ga...@google.com> #22Jul 30, 2018 08:26AM

Re #21: I think this might be

https://issuetracker.google.com/78108767.

do...@gmail.com <do...@gmail.com> #23Jul 30, 2018 02:57PM

Re #22: The problem seems similar but it does not solve my problem. The project you provided did not even use orchestrator.
I cannot find a fix yet. Any other suggestions?

Thanks.

ga...@google.com <ga...@google.com> #24Jul 30, 2018 03:08PM

Re #23: Can you please upload a sample project that reproduces the issue? It looks like the test runner cannot find the test classes in the test APK.

do...@gmail.com <do...@gmail.com> #25Jul 30, 2018 03:29PM

I cannot show you the code of my main project but this is a test project that mimics the same problem in my main project.
If I use orchestrator:1.0.1 (line 112), I can run the test cases with the tasks "createProductionDebugCoverageReport" (./gradlew createProductionDebugCoverageReport).
If I use orchestrator:1.0.2 without changing anything in the test cases, it throws me an error as I mentioned before.

Let me know if you need more information.

Android-Jacoco.zip

72 MB

Download

ga...@google.com <ga...@google.com> #26Jul 30, 2018 03:42PM

As #17 says, you need to use the Android Gradle plugin 3.2.0-alpha17 or higher. This fix is not ported to 3.1 versions of the plugin. Updating your sample project to use 3.2.0-beta04 fixes the issue.

do...@gmail.com <do...@gmail.com> #27Jul 30, 2018 05:36PM

AHHH.. my bad!! I thought it was talking about the gradle version.

It fixed this problem but had a different problem. I will open a new post if I don't find a fix for that.

Thanks man.

sh...@gmail.com <sh...@gmail.com> #28Aug 6, 2018 11:20AM

Hi
I have used: gradle: 3.2.0-alpha17, test:runner: 1.0.2
distributionUrl=https\://

services.gradle.org/distributions/gradle-4.6-all.zip
testInstrumentationRunnerArguments clearPackageData: 'true'
execution 'ANDROID_TEST_ORCHESTRATOR'
androidTestUtil 'com.android.support.test:orchestrator:1.0.1'

Jacaoco setup -
task jacocoTestReport(type: JacocoReport, dependsOn: ['testDebugUnitTest', 'createDebugCoverageReport']) {

reports {
xml.enabled = true
html.enabled = true
}
fileFilter ="***"
def debugTree = fileTree(dir: "${buildDir}/intermediates/classes/debug", excludes: fileFilter)
def mainSrc = "${project.projectDir}/src/main/java"

sourceDirectories = files([mainSrc])
classDirectories = files([debugTree])
executionData = fileTree(dir: "$buildDir", includes: [
"jacoco/testDebugUnitTest.exec",
"outputs/code-coverage/connected/*

coverage.ec"
----

allprojects {
apply plugin: "jacoco"
jacoco {
toolVersion = "0.8.0"
}
-----
dependencies {
classpath 'com.android.tools.build:gradle:3.2.0-alpha17'
classpath "org.jacoco:org.jacoco.core:0.8.0"

-----

I am getting the Following Error

C:\Development\Projects\BreathMapper\Workspace\Source\BreatheMapper\app\libs\adobeMobileLibrary-4.13.5.jar
Warning:Type `com.google.android.gms.wearable.PutDataMapRequest` was not found, it is required for default or static interface methods desugaring of `void com.adobe.mobile.ConfigSynchronizer.syncData(java.lang.String, com.google.android.gms.wearable.DataMap)`
Warning:Type `com.google.android.gms.wearable.DataMapItem` was not found, it is required for default or static interface methods desugaring of `void com.adobe.mobile.ConfigSynchronizer.restoreConfig(com.google.android.gms.wearable.DataItem)`
Warning:Type `com.google.android.gms.wearable.PutDataMapRequest` was not found, it is required for default or static interface methods desugaring of `com.adobe.mobile.WearableDataResponse com.adobe.mobile.WearableDataConnection.send(com.adobe.mobile.WearableDataRequest)`
Warning:Type `com.google.android.gms.wearable.DataMapItem` was not found, it is required for default or static interface methods desugaring of `void com.adobe.mobile.WearableDataConnection.onDataChanged(com.google.android.gms.wearable.DataEventBuffer)`
Warning:Type `com.google.android.gms.wearable.Asset` was not found, it is required for default or static interface methods desugaring of `com.google.android.gms.wearable.DataMap com.adobe.mobile.WearableDataRequest$Cache.handle(android.content.Context)`
Warning:Interface `com.google.android.gms.common.api.GoogleApiClient$OnConnectionFailedListener` not found. It's needed to make sure desugaring of `com.adobe.mobile.WearableDataConnection` is correct. Desugaring will assume that this interface has no default method.
Warning:Interface `com.google.android.gms.wearable.DataApi$DataListener` not found. It's needed to make sure desugaring of `com.adobe.mobile.WearableDataConnection` is correct. Desugaring will assume that this interface has no default method.
C:\Users\xx\.gradle\caches\transforms-1\files-1.1\runtime-1.1.1.aar\be15bb0ad7b260a4de5c6f23e94be8e7\jars\classes.jar
Warning:Type `android.arch.paging.PositionalDataSource` was not found, it is required for default or static interface methods desugaring of `boolean android.arch.persistence.room.paging.LimitOffsetDataSource.isInvalid()`
C:\Users\xx\.gradle\caches\transforms-1\files-1.1\espresso-core-3.0.2.aar\f93273e747e9ce9e35d6f1173bb60539\jars\classes.jar
Warning:Type `sun.misc.Unsafe` was not found, it is required for default or static interface methods desugaring of `sun.misc.Unsafe android.support.test.espresso.core.internal.deps.guava.cache.Striped64.getUnsafe()`
Warning:Type `sun.misc.Unsafe` was not found, it is required for default or static interface methods desugaring of `void android.support.test.espresso.core.internal.deps.guava.util.concurrent.AbstractFuture$UnsafeAtomicHelper.<clinit>()`
Error:
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 warning
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:createDebugAndroidTestCoverageReport'.
> java.io.IOException: No coverage data to process in directory 'C:\Development\Projects\BreathMapper\Workspace\Source\BreatheMapper\app\build\outputs\code-coverage\connected'

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at

https://help.gradle.org

BUILD FAILED in 4m 56s

NoEcFile.png

11 KB

View

Download

ga...@google.com <ga...@google.com> #29Aug 6, 2018 12:41PM

Re #28:
Can you please file a new issue, and upload a sample project that reproduces it?

sh...@gmail.com <sh...@gmail.com> #30Aug 6, 2018 12:43PM

Continued Re #28
Full Error log
C:\Development\Projects\MyTest\Workspace\Source\MyTest\app\build\outputs\androidTest-results\connected\TEST-Galaxy_Nexus_API_26(AVD) - 8.0.0-app-.xml. Total tests 48, passed 48,
06:04:55 V/ddms: execute 'CLASSPATH=$(pm path android.support.test.services) app_process / android.support.test.services.shellexecutor.ShellMain am instrument -r -w -e targetInstrumentation com.vn.test.test/android.support.test.runner.AndroidJUnitRunner --no_window_animation -e coverageFilePath /data/data/com.vn.test/coverage_data/ -e coverage true android.support.test.orchestrator/android.support.test.orchestrator.AndroidTestOrchestrator' on 'emulator-5556' : EOF hit. Read: -1
06:04:55 V/ddms: execute: returning
06:04:55 V/ddms: execute: running echo 'for i in $(run-as com.vn.test ls /data/data/com.vn.test/coverage_data/); do run-as com.vn.test cat /data/data/com.vn.test/coverage_data/$i > /data/local/tmp/com.vn.test-coverage_data/$i; done' > /data/local/tmp/com.vn.test-coverage_data/copyFromUser.sh
06:04:55 V/ddms: execute 'echo 'for i in $(run-as com.vn.test ls /data/data/com.vn.test/coverage_data/); do run-as com.vn.test cat /data/data/com.vn.test/coverage_data/$i > /data/local/tmp/com.vn.test-coverage_data/$i; done' > /data/local/tmp/com.vn.test-coverage_data/copyFromUser.sh' on 'emulator-5556' : EOF hit. Read: -1
06:04:55 V/ddms: execute: returning
06:04:55 V/ddms: execute: running sh /data/local/tmp/com.vn.test-coverage_data/copyFromUser.sh
06:04:55 V/ddms: execute 'sh /data/local/tmp/com.vn.test-coverage_data/copyFromUser.sh' on 'emulator-5556' : EOF hit. Read: -1
06:04:55 V/ddms: execute: returning
06:04:55 V/ddms: execute: running ls /data/local/tmp/com.vn.test-coverage_data > /data/local/tmp/com.vn.test-coverage_data/paths.txt
06:04:55 V/ddms: execute 'ls /data/local/tmp/com.vn.test-coverage_data > /data/local/tmp/com.vn.test-coverage_data/paths.txt' on 'emulator-5556' : EOF hit. Read: -1
06:04:55 V/ddms: execute: returning
06:04:55 D/paths.txt: Downloading paths.txt from device 'emulator-5556'
06:04:55 D/Device: Downloading file from device 'emulator-5556'
06:04:55 V/ddms: execute: running rm -r /data/local/tmp/com.vn.test-coverage_data
06:04:55 V/ddms: execute 'rm -r /data/local/tmp/com.vn.test-coverage_data' on 'emulator-5556' : EOF hit. Read: -1
06:04:55 V/ddms: execute: returning
06:04:55 V/ddms: execute: running pm uninstall com.vn.test.test
06:04:55 V/ddms: execute 'pm uninstall com.vn.test.test' on 'emulator-5556' : EOF hit. Read: -1
06:04:55 V/ddms: execute: returning
06:04:55 V/ddms: execute: running pm uninstall com.vn.test
06:04:56 V/ddms: execute 'pm uninstall com.vn.test' on 'emulator-5556' : EOF hit. Read: -1
06:04:56 V/ddms: execute: returning
:app:createDebugAndroidTestCoverageReport FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:createDebugAndroidTestCoverageReport'.
> java.io.IOException: No coverage data to process in directory 'C:\Development\Projects\MyTest\Workspace\Source\Test\app\build\outputs\code-coverage\connected'

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at

https://help.gradle.org

BUILD FAILED in 3m 14s

sh...@gmail.com <sh...@gmail.com> #31Aug 6, 2018 12:46PM

@ Re #29:
I have uploaded some more log detail.

sh...@gmail.com <sh...@gmail.com> #32Aug 6, 2018 12:56PM

Re #29

My setup was working fine with earlier gradle plugin 3.1.2 . with distributionUrl=gradle-4.4-all.zip (.ec file was generating but only coverage data is incomplete ).
But I tried to implement the solution provided in #20
gradle plugin - gradle:3.2.0-alpha17' with distributionUrl=gradle-4.6-all.zip But getting #30 error an .ec file not generating

ga...@google.com <ga...@google.com> #33Aug 6, 2018 01:15PM

Re #32: Please file a new issue, as it looks different than the original one. We can continue the discussion there.

sh...@gmail.com <sh...@gmail.com> #34Aug 7, 2018 06:29AM

Re#33: Created. Thanks, Link :

https://issuetracker.google.com/issues/112272957

ba...@gmail.com <ba...@gmail.com> #35Jan 2, 2019 06:05AM

Hi,
How to test the private methods and greendao database CRUD operations in android robolectric test case.
How to get private method code coverage in android jacoco library using

sl...@gmail.com <sl...@gmail.com> #36Feb 6, 2019 11:46AM

I can confirm this is still a problem...

> java.io.IOException: No coverage data to process in directories [[/Users/msh/git/wine-scanner-android/app/build/outputs/code_coverage/worldDebugAndroidTest/connected]]

Only happens when enabling ANDROIDX_TEST_ORCHESTRATOR

ga...@google.com <ga...@google.com> #37Feb 6, 2019 11:56AM

Re #36:
Can you please share a project the reproduces the issue?

sl...@gmail.com <sl...@gmail.com> #38Feb 6, 2019 01:02PM

Not really as its the project at the company where I work. Its a huge project so not small task to maintain - hence the need for test coverage...

I've tried trouble shooting most of the day and so far no luck. I really have no idea where to start looking.

Not sure if it will help but the complete output when running ./gradlew createWorldDebugCoverageReport is attached.

I've tried against an emulator (genymotion) as well as a real device - same result.

I guess the next logical step is to setup a basic project and see if that has the same problem...

output.txt

30 KB

View

Download

output_debug.txt

57 MB

View

Download

ga...@google.com <ga...@google.com> #39Feb 6, 2019 04:17PM

I've opened a new issue,

https://issuetracker.google.com/123987001, because this differs from the original problem in this issue.

bi...@gmail.com <bi...@gmail.com> #40Mar 20, 2019 03:52PM

Env. androidx.test:orchestrator:1.1.1
Still error
Execution failed for task ':app:createDebugAndroidTestCoverageReport'.
> java.io.IOException: No coverage data to process in directories /app/build/outputs/code_coverage/debugAndroidTest/connected

sl...@gmail.com <sl...@gmail.com> #41Mar 24, 2019 01:22PM

Did you remove the clearPackageData option ?

az...@gmail.com <az...@gmail.com> #42Jul 17, 2019 06:53AM

I can confirm, that I also have issue with JaCoCo report with following error log:

> Caused by: org.gradle.api.UncheckedIOException: java.io.IOException: No coverage data to process in directories [[/Users/azizbekian/Projects/XXX/XXX/app/build/outputs/code_coverage/devDebugAndroidTest/connected]]

Using `androidTestUtil androidx.test:orchestrator:1.2.0`
AGP version 3.4.2
Gradle version 5.5
Have specified `testInstrumentationRunnerArguments clearPackageData: 'true'` in `defaultConfig` DSL
Have specified `execution 'ANDROIDX_TEST_ORCHESTRATOR'` in testOptions DSL

Problem is, that I cannot see `

coverage.ec` file being created in /code_coverage/devDebugAndroidTest/connected/ directory.

Screen Shot 2019-07-17 at 10.51.25 AM.png

62 KB

View

Download

an...@gmail.com <an...@gmail.com> #43Feb 18, 2020 09:32AM

Have any update for this issue? I'm also getting the same issue when run jacoco: java.io.IOException: No coverage data to process in directories

bj...@googlemail.com <bj...@googlemail.com> #44Feb 28, 2020 03:52PM

I'm interested in a solution, too. If I cannot use the orchestrator, how can I make sure my tests are independent?

ma...@gmail.com <ma...@gmail.com> #45May 16, 2020 12:31PM

This is ridiculous. How can it not been fixed after more than 2 years?
Running tests and having coverage data is a basic scenario for every developer that has some self-respect.

sc...@gmail.com <sc...@gmail.com> #46Jun 4, 2020 01:48PM

I'm also running into this issue, can we get an update on this?

eu...@rbs.co.uk <eu...@rbs.co.uk> #47Jun 4, 2020 03:39PM

But this isn't fixed. When clearPackageData is true, the coverage data is deleted.

wi...@gmail.com <wi...@gmail.com> #48Jun 29, 2020 10:11PM

Please, is there any update on this?

ga...@google.com <ga...@google.com> #49Jun 30, 2020 08:20AM

The root cause of this issue has been fixed, and you are almost certainly hitting another issue. Please open a new bug to help us track issues in a better way.

[Deleted User] <[Deleted User]> #50Jun 30, 2020 03:14PM

At it again, Google? Giving vague answers about things being fixed with no real details to the users subscribed to the issue. Looks like they "fixed" it by making the "path" option work properly so you can specify the path. Mind you, I still have not gotten a chance to try this yet as the last time they said they fixed this I spent hours of my life trying to make it work without the required details. Didn't realize they had this split into two tickets so they could absolutely confuse *two* groups of people. See my comment on the other issue

https://issuetracker.google.com/issues/123987001#comment17

ga...@google.com <ga...@google.com> #51Jun 30, 2020 03:33PM

Please read all comments before posting, as comment #17 clearly specifies AGP version which includes the fix. Bugs have been split to allow easier tracking. The issue which you perceive as one (coverage not working with test orchestrator) had multiple underlying problems, and one of them was fixed here. The other one was fixed in https://issuetracker.google.com/123987001.

[Deleted User] <[Deleted User]> #52Jun 30, 2020 04:21PM

and to you, please provide relevant information to your users when posting "fixed". Thank you.

Issue 72758547

Description

Issue summary

Comments

gg...@google.com <gg...@google.com> Feb 5, 2018 02:55PM

gg...@google.com <gg...@google.com> #2Feb 6, 2018 06:04AM

[Deleted User] <[Deleted User]> #3Feb 21, 2018 07:59PM

ay...@blink22.com <ay...@blink22.com> #4Feb 22, 2018 11:24AM

be...@gmail.com <be...@gmail.com> #5Feb 25, 2018 06:47PM

so...@gmail.com <so...@gmail.com> #6Feb 27, 2018 03:20PM

ga...@google.com <ga...@google.com> #7Feb 27, 2018 03:31PM

nk...@google.com <nk...@google.com> #8Feb 27, 2018 07:19PM

ay...@blink22.com <ay...@blink22.com> #9Mar 20, 2018 01:03PM

nk...@google.com <nk...@google.com> Mar 20, 2018 05:23PM

ju...@gmail.com <ju...@gmail.com> #10Mar 28, 2018 01:01AM

nk...@google.com <nk...@google.com> #11Mar 28, 2018 05:50AM

nk...@google.com <nk...@google.com> #12Mar 28, 2018 07:01PM

[Deleted User] <[Deleted User]> #13Apr 15, 2018 09:57AM

nk...@google.com <nk...@google.com> #14Apr 16, 2018 05:46PM

ga...@google.com <ga...@google.com> May 1, 2018 05:11PM

[Deleted User] <[Deleted User]> #15May 7, 2018 10:48PM

ga...@google.com <ga...@google.com> #16May 8, 2018 09:24AM

ga...@google.com <ga...@google.com> #17May 18, 2018 08:01AM

co...@gmail.com <co...@gmail.com> #18May 23, 2018 01:59PM

sl...@google.com <sl...@google.com> #19May 23, 2018 07:10PM

is...@gmail.com <is...@gmail.com> #20Jul 1, 2018 01:43PM

do...@gmail.com <do...@gmail.com> #21Jul 27, 2018 06:31PM

ga...@google.com <ga...@google.com> #22Jul 30, 2018 08:26AM

do...@gmail.com <do...@gmail.com> #23Jul 30, 2018 02:57PM

ga...@google.com <ga...@google.com> #24Jul 30, 2018 03:08PM

do...@gmail.com <do...@gmail.com> #25Jul 30, 2018 03:29PM

ga...@google.com <ga...@google.com> #26Jul 30, 2018 03:42PM

do...@gmail.com <do...@gmail.com> #27Jul 30, 2018 05:36PM

sh...@gmail.com <sh...@gmail.com> #28Aug 6, 2018 11:20AM

ga...@google.com <ga...@google.com> #29Aug 6, 2018 12:41PM

sh...@gmail.com <sh...@gmail.com> #30Aug 6, 2018 12:43PM

sh...@gmail.com <sh...@gmail.com> #31Aug 6, 2018 12:46PM

sh...@gmail.com <sh...@gmail.com> #32Aug 6, 2018 12:56PM

ga...@google.com <ga...@google.com> #33Aug 6, 2018 01:15PM

sh...@gmail.com <sh...@gmail.com> #34Aug 7, 2018 06:29AM

ba...@gmail.com <ba...@gmail.com> #35Jan 2, 2019 06:05AM

sl...@gmail.com <sl...@gmail.com> #36Feb 6, 2019 11:46AM

ga...@google.com <ga...@google.com> #37Feb 6, 2019 11:56AM

sl...@gmail.com <sl...@gmail.com> #38Feb 6, 2019 01:02PM

ga...@google.com <ga...@google.com> #39Feb 6, 2019 04:17PM

bi...@gmail.com <bi...@gmail.com> #40Mar 20, 2019 03:52PM

sl...@gmail.com <sl...@gmail.com> #41Mar 24, 2019 01:22PM

az...@gmail.com <az...@gmail.com> #42Jul 17, 2019 06:53AM

an...@gmail.com <an...@gmail.com> #43Feb 18, 2020 09:32AM

bj...@googlemail.com <bj...@googlemail.com> #44Feb 28, 2020 03:52PM

ma...@gmail.com <ma...@gmail.com> #45May 16, 2020 12:31PM

sc...@gmail.com <sc...@gmail.com> #46Jun 4, 2020 01:48PM

eu...@rbs.co.uk <eu...@rbs.co.uk> #47Jun 4, 2020 03:39PM

wi...@gmail.com <wi...@gmail.com> #48Jun 29, 2020 10:11PM

ga...@google.com <ga...@google.com> #49Jun 30, 2020 08:20AM

[Deleted User] <[Deleted User]> #50Jun 30, 2020 03:14PM

ga...@google.com <ga...@google.com> #51Jun 30, 2020 03:33PM

[Deleted User] <[Deleted User]> #52Jun 30, 2020 04:21PM

Add comment

Issue metadata