[GRADLE-3403] Error "failed to abort Gradle Compiler Daemon 2" gets printed to console when build is terminated with CTRL-C Created: 18/Feb/16  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Lari Hotari Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

An error "failed to abort Gradle Compiler Daemon 2" gets printed to console when build is terminated with CTRL-C. This might not happen in all environments and OSs.

:wrapper:sourceJar
:wrapper:publishLocalArchives
> :integTest:integTest
failed to abort Gradle Compiler Daemon 2
java.lang.IllegalStateException: Cannot abort process 'Gradle Compiler Daemon 2' because it is not in started or detached state
        at org.gradle.process.internal.DefaultExecHandle.abort(DefaultExecHandle.java:262)
        at org.gradle.process.internal.ExecHandleShutdownHookAction.run(ExecHandleShutdownHookAction.java:39)
        at org.gradle.process.internal.shutdown.ShutdownHookActionRegister$GradleShutdownHook.run(ShutdownHookActionRegister.java:41)
        at java.lang.Thread.run(Thread.java:745)
> Building 92% > :integTest:integTest > 102 tests completed, 4 skipped

It seems to be a race condition in DefaultExecHandle . Pressing CTRL-C will kill the child processes and the process might have been killed/finished when the shutdown hook tries to abort the running process.

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