[GRADLE-1902] Gradle hangs when running TestNG on FreeBSD Created: 08/Nov/11 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | 0.9-rc-3, 1.0-milestone-3 |
Fix Version/s: | None |
Type: | Bug | ||
Reporter: | Nikita Skvortsov | Assignee: | Unassigned |
Resolution: | Won't Fix | Votes: | 0 |
Attachments: | gradleProj.zip stacktrace.txt thread_dump.txt |
Description |
When trying to run test with TestNG framework, Gradle reports successfull build and then hangs forever. Sample project and thread dump attached. |
Comments |
Comment by Adam Murdoch [ 28/Jan/13 ] |
This should be fixed now. Can you try it out with Gradle 1.4 and let us know if the problem still exists? |
Comment by Nikita Skvortsov [ 11/Feb/13 ] |
I would be glad to check it, but with 1.4 Gradle wrapper seems to be failing. Something related to filesystem. Environment is FreeBSD 7.1-RELEASE-p11, filesystem is "ufs". I will attach stacktrace now. |
Comment by Nikita Skvortsov [ 11/Feb/13 ] |
Gradle Wrapper stacktrace for FreeBSD |
Comment by Adam Murdoch [ 19/Mar/13 ] |
Can you tell me which version of FreeBSD you are using and which architecture? |
Comment by Nikita Skvortsov [ 20/Mar/13 ] |
Here is "uname -a" output: FreeBSD freebsd-2 7.1-RELEASE-p11 FreeBSD 7.1-RELEASE-p11 #0: Fri Feb 26 18:34:31 UTC So it is 7.1-RELEASE-p11 on i386 |
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. |