[GRADLE-3001] applying jacoco plugin may lead to test failures Created: 22/Jan/14  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.10
Fix Version/s: None

Type: Bug
Reporter: Szczepan Faber Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

Jacoco plugin adds agent settings to test task vm regardless if we're running jacoco reports. This means that when the plugin is applied, by default all "test" tasks will be execute tests in a vm with the agent. I found that it has some awkward effect on certain tests. Basically, some tests started failing (could be a jacoco bug):

java.lang.IllegalArgumentException: Failed to instantiate override type: class xxx.R2ClientFactory$Overrides. Errors: [Found private field reachable from override class: class xxx.R2ClientFactory$Overrides.$jacocoData, Found static field reachable from override class: class xxx.R2ClientFactory$Overrides.$jacocoData]

It feels that to be a good citizen, jacoco plugin should not alter the behavior of tests, when we are not tracking coverage. It feels that the most natural approach is: when we run jacoco reports the tests are executed with the agent; when we just run tests, the jacoco agent is not involved. Obviously, the user can configure the agent to be involved in every test execution. However, I don't think it should be the default.

 Comments   
Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:37:12 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.