You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Steps: (what exactly are you doing with the above reproducer?)
Run ./gradlew jacocoTestReportDebug in the provided sample, or just open the jacoco report that should already be included from when I ran it app/build/reports/jacoco/debug/com.example.coroutinelaunch/ExampleRepository.kt.html
Expected behaviour
ExampleRepository.kt should have 100% coverage.
Actual behaviour
The call to CoroutineScope.launch is marked partially covered, I believe from the theoretically possible case where the coroutine somehow doesn't get launched.
ExampleRepository.doSomething.new Function2() {...}invokeSuspend(Object) is what I see marked as not covered.
I believe this to be a barebones reproducible version of #1290 which was closed for not having a sample. It is my understanding that 0.8.7 release should have fixed this this issue with the inclusion of #1149.
Steps to reproduce
Steps: (what exactly are you doing with the above reproducer?)
./gradlew jacocoTestReportDebug
in the provided sample, or just open the jacoco report that should already be included from when I ran itapp/build/reports/jacoco/debug/com.example.coroutinelaunch/ExampleRepository.kt.html
Expected behaviour
ExampleRepository.kt
should have 100% coverage.Actual behaviour
The call to
CoroutineScope.launch
is marked partially covered, I believe from the theoretically possible case where the coroutine somehow doesn't get launched.ExampleRepository.doSomething.new Function2() {...}
invokeSuspend(Object)
is what I see marked as not covered.I believe this to be a barebones reproducible version of #1290 which was closed for not having a sample. It is my understanding that 0.8.7 release should have fixed this this issue with the inclusion of #1149.
See also this issue from the kotlin coroutines repo: Kotlin/kotlinx.coroutines#2351
The text was updated successfully, but these errors were encountered: