-
Bug
-
Resolution: Duplicate
-
Minor
-
None
Whenever I run the build, it creates following errors:
2017-02-24T05:03:24.106609502Z Feb 24, 2017 5:03:24 AM io.fabric8.kubernetes.client.utils.InputStreamPumper run 2017-02-24T05:03:24.106641810Z SEVERE: Error while pumping stream. 2017-02-24T05:03:24.106645779Z java.io.IOException: Pipe broken 2017-02-24T05:03:24.106649106Z at java.io.PipedInputStream.read(PipedInputStream.java:321) 2017-02-24T05:03:24.106652227Z at java.io.PipedInputStream.read(PipedInputStream.java:377) 2017-02-24T05:03:24.106655369Z at java.io.InputStream.read(InputStream.java:101) 2017-02-24T05:03:24.106658245Z at io.fabric8.kubernetes.client.utils.InputStreamPumper.run(InputStreamPumper.java:48) 2017-02-24T05:03:24.106661089Z at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 2017-02-24T05:03:24.106663857Z at java.util.concurrent.FutureTask.run(FutureTask.java:266) 2017-02-24T05:03:24.106666697Z at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 2017-02-24T05:03:24.106669388Z at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 2017-02-24T05:03:24.106672142Z at java.lang.Thread.run(Thread.java:745)
Is there a reason why this is happening and how can we avoid such errors?
- duplicates
-
JENKINS-40825 "Pipe not connected" errors when running multiple builds simultaneously
-
- Resolved
-