[GRADLE-3144] IllegalAccessError from Javac classes when running tests Created: 31/Jul/14  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Radim Kubacki Assignee: Radim Kubacki
Resolution: Won't Fix Votes: 0


 Description   

Windows 7 + JDK1.6.

  • clone our repository git@github.com:gradle/gradle.git at revision c2019ec57483545ec443bf56cf34b96e7a86ea19 (test is enabled there)
  • run './gradlew clean :toolingApi:integTest -PmaxParallelForks=3'

4 tests in SamplesToolingApiIntegrationTest will fail with a stack trace like https://gist.github.com/radimk/7143446

The same command passes on Linux/JDK1.6 or with JDK1.7 (though I have seen it with Java 7 too with some other test but cannot reproduce). It also cannot be reproduced if I change maxParallelForks parameter and it means that the particular order of tests triggers it. Under the assumption that it is related to http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7012161 I tried to change -Xmx for our test executor to values between 480M-1024M and it always fails in the same way.

 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:41:07 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.