運行Gradle測試時出現斷管錯誤

我在Gradle中運行測試時遇到了問題。我知道在其他機器上，我的gradle配置工作，但不幸的是我不是。我們有JUnit測試和TestNG和他們兩個，當嘗試執行，產生堆棧跟蹤是這樣的：運行Gradle測試時出現斷管錯誤

Could not write standard input into: Gradle Worker 1. 
java.io.IOException: The pipe is being closed 
    at java.io.FileOutputStream.writeBytes(Native Method) 
    at java.io.FileOutputStream.write(FileOutputStream.java:318) 
    at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82) 
    at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140) 
    at org.gradle.process.internal.streams.ExecOutputHandleRunner.run(ExecOutputHandleRunner.java:53) 
    at org.gradle.internal.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:66) 
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 
    at java.lang.Thread.run(Thread.java:722)

它連續地會產生這個錯誤有不同的數字（搖籃工人2，搖籃工人3等）。有沒有人遇到類似的問題？

我使用gradle 1.6。

編輯：我忘了告訴我使用gradle這個包裝

編輯：切換到1.12版本後我收到錯誤：

Caused by: org.gradle.api.InvalidUserDataException: Could not create task '(custome taks name)': Unknown argument(s) in task definition: [mustRunAfter] 
11:20:17.990 [ERROR] [org.gradle.BuildExceptionReporter] at org.gradle.api.internal.project.taskfactory.TaskFactory.validateArgs(TaskFactory.java:147) 
11:20:17.991 [ERROR] [org.gradle.BuildExceptionReporter] at org.gradle.api.internal.project.taskfactory.TaskFactory.checkTaskArgsAndCreateDefaultValues(TaskFactory.java:134) 
11:20:17.991 [ERROR] [org.gradle.BuildExceptionReporter] at org.gradle.api.internal.project.taskfactory.TaskFactory.createTask(TaskFactory.java:72)

編輯：好的，我想我已經找到了導致此問題 - 它是防病毒。當我將其禁用腳本移動一點點的進步，但與同期：

org.gradle.messaging.remote.internal.ConnectException: Could not connect to server [e42b57ea-ced6-4bb6-9369-3186ab4983d6 port:63631, addresses:[/127.0.0.1, /0:0:0:0:0:0:0:1]]. Tried addresses: [/127.0.0.1, /0:0:0:0:0:0:0:1]. 
    at org.gradle.messaging.remote.internal.inet.TcpOutgoingConnector.connect(TcpOutgoingConnector.java:62) 
    at org.gradle.messaging.remote.internal.hub.MessageHubBackedClient.getConnection(MessageHubBackedClient.java:35) 
    at org.gradle.process.internal.child.ActionExecutionWorker.execute(ActionExecutionWorker.java:54) 
    at org.gradle.process.internal.child.ActionExecutionWorker.execute(ActionExecutionWorker.java:35) 
    at org.gradle.process.internal.child.ImplementationClassLoaderWorker.execute(ImplementationClassLoaderWorker.java:85) 
    at org.gradle.process.internal.child.ImplementationClassLoaderWorker.execute(ImplementationClassLoaderWorker.java:41) 
    at org.gradle.process.internal.child.SystemApplicationClassLoaderWorker.call(SystemApplicationClassLoaderWorker.java:43) 
    at org.gradle.process.internal.child.SystemApplicationClassLoaderWorker.call(SystemApplicationClassLoaderWorker.java:32) 
    at org.gradle.process.internal.launcher.BootstrapClassLoaderWorker.call(BootstrapClassLoaderWorker.java:46) 
    at org.gradle.process.internal.launcher.BootstrapClassLoaderWorker.call(BootstrapClassLoaderWorker.java:32) 
    at jarjar.org.gradle.process.internal.launcher.GradleWorkerMain.run(GradleWorkerMain.java:32) 
    at jarjar.org.gradle.process.internal.launcher.GradleWorkerMain.main(GradleWorkerMain.java:37) 
Caused by: java.net.ConnectException: Connection refused: connect

與此錯誤谷歌搜索給我什麼（只有一些老gradle這個1.1的錯誤信息）。有人遇到這種問題嗎？

來源

2014-07-03 PastorPL

我會嘗試使用最新的Gradle版本。 –

嘗試gradle 1.12 –

1.12錯誤可能意味着在構建腳本中有一個錯誤在1.6中未被發現。 –

經過一整天與gradle的鬥爭，我終於找到了導致問題的原因。這是犯罪的殺毒軟件 - COMODO。卸載它並安裝另一個之後，一切都開始正常工作。所以所有的Gradle用戶 - 請小心COMODO，因爲即使禁用，使用Gradle時可能會導致問題。請注意:)

來源

2014-07-04 08:43:33 PastorPL

運行Gradle測試時出現斷管錯誤

回答

相關問題