[GRADLE-2651] test worker process failures are hard to diagnose Created: 23/Jan/13  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

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


There are a couple of problems with failure behavior of the test worker process. I can observe them with TestNG but they might be also reproducable with JUnit.

If the user test runtime classpath contains conflicted libraries here's what may happen:

1. Gradle fails the build saying that 'some tests failed' and pointing out to the html report. This is wrong on its own because there's no report and no tests have been run. This is already reported here: GRADLE-1710
2. Gradle does not show useful stack trace with -s. It only informs that the worker process misbehaved. The only way to find out why the worker process misbehaved is to run with --debug but it is inconvenient because -d output is hard to investigate (lots of stuff).
3. The debug output when investigated shows:

  • First, TestNGTestResultProcessorAdapter fails in constructor (root cause being java.lang.VerifyError or something smiliar)
  • Then, there are various NPE stack traces, possibly caused by the earlier TestNGTestResultProcessorAdapter failure
  • I would expect to see only a relevant stack trace (no NPEs)

The debug output from the reproducible sample is here: https://gist.github.com/46f391499ed5c418810e The problem in the sample was that there was both: google-collections and guava on the test runtime classpath and this combination was causing java.lang.VerifyError.

The user who reported this issue originally was convinced that it was a Gradle problem and the root cause was incompatibility of Gradle's classpath (which has guava) with test runtime classpath.

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