[GRADLE-1725] Nested exception in failing test case causes ClassCastException in gradle Created: 05/Aug/11 Updated: 10/Feb/17 Resolved: 10/Feb/17
|Affects Version/s:||1.0-milestone-3, 1.0-milestone-4|
We recently switched from ant/ivy to gradle. When one of our testng integration tests failed with a DB constraint exception, gradle was disconnecting and failing to report it properly. The exception in the failing test case causes a ClassCastException in gradle.
Attached simple example that simulates issue. Gradle should report one failing test and one passing test.
|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:
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.