[JBoss JIRA] (JBIDE-26018) 'Remediation' when installing JBT into Eclipse Photon M6
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26018?page=com.atlassian.jira.plugi... ]
Pavol Srna reassigned JBIDE-26018:
----------------------------------
Assignee: Nick Boldt
> 'Remediation' when installing JBT into Eclipse Photon M6
> --------------------------------------------------------
>
> Key: JBIDE-26018
> URL: https://issues.jboss.org/browse/JBIDE-26018
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: updatesite
> Affects Versions: 4.6.0.AM1
> Environment: eclipse-jee-photon-M6
> Reporter: Pavol Srna
> Assignee: Nick Boldt
> Fix For: 4.6.0.AM2
>
>
> {code}
> Your original request has been modified.
> "JavaScript Development Tools" is already installed, so an update will be performed instead.
> "Eclipse JSON Editors and Tools" is already installed, so an update will be performed instead.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: Eclipse JSON Editors and Tools 1.1.2.v201804101953 (org.eclipse.wst.json_ui.feature.feature.group 1.1.2.v201804101953)
> Software currently installed: Eclipse Web Developer Tools 3.9.2.v201802261859 (org.eclipse.wst.web_ui.feature.feature.group 3.9.2.v201802261859)
> Only one of the following can be installed at once:
> Eclipse JSON Editors and Tools 1.1.2.v201804101953 (org.eclipse.wst.json_ui.feature.feature.jar 1.1.2.v201804101953)
> Eclipse JSON Editors and Tools 1.1.0.v201704192002 (org.eclipse.wst.json_ui.feature.feature.jar 1.1.0.v201704192002)
> Eclipse JSON Editors and Tools 1.0.0.v201609072018 (org.eclipse.wst.json_ui.feature.feature.jar 1.0.0.v201609072018)
> Eclipse JSON Editors and Tools 3.8.0.v201601291607 (org.eclipse.wst.json_ui.feature.feature.jar 3.8.0.v201601291607)
> Eclipse JSON Editors and Tools 1.0.0.v201603042101 (org.eclipse.wst.json_ui.feature.feature.jar 1.0.0.v201603042101)
> Eclipse JSON Editors and Tools 1.0.0.v201604280217 (org.eclipse.wst.json_ui.feature.feature.jar 1.0.0.v201604280217)
> Eclipse JSON Editors and Tools 1.0.0.v201605251755 (org.eclipse.wst.json_ui.feature.feature.jar 1.0.0.v201605251755)
> Eclipse JSON Editors and Tools 1.1.2.v201802171654 (org.eclipse.wst.json_ui.feature.feature.jar 1.1.2.v201802171654)
> Cannot satisfy dependency:
> From: Eclipse JSON Editors and Tools 1.1.2.v201802171654 (org.eclipse.wst.json_ui.feature.feature.group 1.1.2.v201802171654)
> To: org.eclipse.equinox.p2.iu; org.eclipse.wst.json_ui.feature.feature.jar [1.1.2.v201802171654,1.1.2.v201802171654]
> Cannot satisfy dependency:
> From: Eclipse JSON Editors and Tools 1.1.2.v201804101953 (org.eclipse.wst.json_ui.feature.feature.group 1.1.2.v201804101953)
> To: org.eclipse.equinox.p2.iu; org.eclipse.wst.json_ui.feature.feature.jar [1.1.2.v201804101953,1.1.2.v201804101953]
> Cannot satisfy dependency:
> From: Eclipse Web Developer Tools 3.9.2.v201802261859 (org.eclipse.wst.web_ui.feature.feature.group 3.9.2.v201802261859)
> To: org.eclipse.equinox.p2.iu; org.eclipse.wst.json_ui.feature.feature.group [1.1.2.v201802171654,1.1.2.v201802171654]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-26018) 'Remediation' when installing JBT into Eclipse Photon M6
by Pavol Srna (JIRA)
Pavol Srna created JBIDE-26018:
----------------------------------
Summary: 'Remediation' when installing JBT into Eclipse Photon M6
Key: JBIDE-26018
URL: https://issues.jboss.org/browse/JBIDE-26018
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: updatesite
Affects Versions: 4.6.0.AM1
Environment: eclipse-jee-photon-M6
Reporter: Pavol Srna
Fix For: 4.6.0.AM2
{code}
Your original request has been modified.
"JavaScript Development Tools" is already installed, so an update will be performed instead.
"Eclipse JSON Editors and Tools" is already installed, so an update will be performed instead.
Cannot complete the install because of a conflicting dependency.
Software being installed: Eclipse JSON Editors and Tools 1.1.2.v201804101953 (org.eclipse.wst.json_ui.feature.feature.group 1.1.2.v201804101953)
Software currently installed: Eclipse Web Developer Tools 3.9.2.v201802261859 (org.eclipse.wst.web_ui.feature.feature.group 3.9.2.v201802261859)
Only one of the following can be installed at once:
Eclipse JSON Editors and Tools 1.1.2.v201804101953 (org.eclipse.wst.json_ui.feature.feature.jar 1.1.2.v201804101953)
Eclipse JSON Editors and Tools 1.1.0.v201704192002 (org.eclipse.wst.json_ui.feature.feature.jar 1.1.0.v201704192002)
Eclipse JSON Editors and Tools 1.0.0.v201609072018 (org.eclipse.wst.json_ui.feature.feature.jar 1.0.0.v201609072018)
Eclipse JSON Editors and Tools 3.8.0.v201601291607 (org.eclipse.wst.json_ui.feature.feature.jar 3.8.0.v201601291607)
Eclipse JSON Editors and Tools 1.0.0.v201603042101 (org.eclipse.wst.json_ui.feature.feature.jar 1.0.0.v201603042101)
Eclipse JSON Editors and Tools 1.0.0.v201604280217 (org.eclipse.wst.json_ui.feature.feature.jar 1.0.0.v201604280217)
Eclipse JSON Editors and Tools 1.0.0.v201605251755 (org.eclipse.wst.json_ui.feature.feature.jar 1.0.0.v201605251755)
Eclipse JSON Editors and Tools 1.1.2.v201802171654 (org.eclipse.wst.json_ui.feature.feature.jar 1.1.2.v201802171654)
Cannot satisfy dependency:
From: Eclipse JSON Editors and Tools 1.1.2.v201802171654 (org.eclipse.wst.json_ui.feature.feature.group 1.1.2.v201802171654)
To: org.eclipse.equinox.p2.iu; org.eclipse.wst.json_ui.feature.feature.jar [1.1.2.v201802171654,1.1.2.v201802171654]
Cannot satisfy dependency:
From: Eclipse JSON Editors and Tools 1.1.2.v201804101953 (org.eclipse.wst.json_ui.feature.feature.group 1.1.2.v201804101953)
To: org.eclipse.equinox.p2.iu; org.eclipse.wst.json_ui.feature.feature.jar [1.1.2.v201804101953,1.1.2.v201804101953]
Cannot satisfy dependency:
From: Eclipse Web Developer Tools 3.9.2.v201802261859 (org.eclipse.wst.web_ui.feature.feature.group 3.9.2.v201802261859)
To: org.eclipse.equinox.p2.iu; org.eclipse.wst.json_ui.feature.feature.group [1.1.2.v201802171654,1.1.2.v201802171654]
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25974) CDK 3.4 runtime detection failing
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25974?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-25974:
---------------------------------------
Hm... I tried cdk 3.4.0 and 3.3.0 and both ended up with what Andre reported. So I can replicate even though I am using 12.0.0.-v20180508-1631-B2428 bits which are supposed to have this patched. Reopening then...
> CDK 3.4 runtime detection failing
> ---------------------------------
>
> Key: JBIDE-25974
> URL: https://issues.jboss.org/browse/JBIDE-25974
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.6.0.AM1
>
> Attachments: image-2018-05-07-17-59-59-316.png
>
>
> Runtime detection doesn't work for 3.4.0 with the whitelist. A regex would be better
> steps:
> # EXE: Preferences > JBoss Runtime Detection > Download
> # ASSERT: List of available runtimes shows up, containing CDK 3.4.0
> # EXEC: Choose "CDK 3.4.0" & hit "Next"
> # EXEC: next page: provide credentials & hit "Next"
> # EXEC: next page: accept the terms & hit "Next"
> # EXEC: next page: use the suggested defaults, make sure that "Install folder" is a separate folder (ex. freshly created ~/cdk/) & hit "Finish"
> # ASSERT: wait for the download to finish
> Result:
> The download wont detect the new CDK 3.4.0 that you just downloaded
> !image-2018-05-07-17-59-59-316.png!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25446) Windows/Mac slave gets disconnected during job execution
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25446?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-25446:
---------------------------------------
I see two main causes that are resulting in slave to be disconnected: Network glitch or machine that is being restarted.
In the second case, that covers windows cases, it is very likely to be caused with windows automatic update service, that installs new update and restarts PC right away. If true, this is quite "nasty" behavior because at the time there is devstudio running and other user's processes. Nevertheless, I have send a PR, tried to provision some win 10 images with patch (turning off win update service), images have suffix "-nowu", applied to jenkins node labels: win10vbox16gb and win10-x64, I am running some tests and will monitor jenkins jobs to see if issue occurs again.
> Windows/Mac slave gets disconnected during job execution
> --------------------------------------------------------
>
> Key: JBIDE-25446
> URL: https://issues.jboss.org/browse/JBIDE-25446
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: qa
> Affects Versions: 4.5.2.AM2
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Blocker
> Labels: jenkins
> Fix For: 4.6.0.AM1, 4.6.x
>
>
> During jenkins job execution slaves is disconnected with exception
> {code}
> 19:09:27 19:09:27.096 DEBUG [WorkbenchTestable][AbstractWait] Waiting until shell matching Matcher matching when all matchers match: [Matcher matching widget which text matches: "Problem Occured"] is available....
> 19:09:32 FATAL: command execution failed
> 19:09:32 java.io.IOException: Backing channel 'Channel to /10.8.247.148' is disconnected.
> 19:09:32 at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:191)
> 19:09:32 at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:256)
> 19:09:32 at com.sun.proxy.$Proxy68.isAlive(Unknown Source)
> 19:09:32 at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1043)
> 19:09:32 at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1035)
> 19:09:32 at hudson.Launcher$ProcStarter.join(Launcher.java:399)
> 19:09:32 at hudson.tasks.Maven.perform(Maven.java:367)
> 19:09:32 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
> 19:09:32 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)
> 19:09:32 at hudson.model.Build$BuildExecution.build(Build.java:205)
> 19:09:32 at hudson.model.Build$BuildExecution.doRun(Build.java:162)
> 19:09:32 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
> 19:09:32 at hudson.model.Run.execute(Run.java:1728)
> 19:09:32 at hudson.matrix.MatrixRun.run(MatrixRun.java:146)
> 19:09:32 at hudson.model.ResourceController.execute(ResourceController.java:98)
> 19:09:32 at hudson.model.Executor.run(Executor.java:404)
> 19:09:32 Caused by: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@5af9151e[name=Channel to /10.8.247.148]
> 19:09:32 at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:210)
> 19:09:32 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:635)
> 19:09:32 at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
> 19:09:32 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> 19:09:32 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 19:09:32 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 19:09:32 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 19:09:32 at java.lang.Thread.run(Thread.java:748)
> 19:09:32 Caused by: java.io.IOException: Connection reset by peer
> 19:09:32 at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
> 19:09:32 at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
> 19:09:32 at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
> 19:09:32 at sun.nio.ch.IOUtil.read(IOUtil.java:197)
> 19:09:32 at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
> 19:09:32 at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:142)
> 19:09:32 at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:359)
> 19:09:32 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:564)
> 19:09:32 ... 6 more
> 19:09:32 Build step 'Invoke top-level Maven targets' marked build as failure
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25446) Windows/Mac slave gets disconnected during job execution
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25446?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-25446:
----------------------------------
Sprint: devex #143 January 2018, devex #146 March 2018, devex #147 April 2018, devex #148 April 2018, devex #149 May 2018 (was: devex #143 January 2018, devex #146 March 2018, devex #147 April 2018, devex #148 April 2018)
> Windows/Mac slave gets disconnected during job execution
> --------------------------------------------------------
>
> Key: JBIDE-25446
> URL: https://issues.jboss.org/browse/JBIDE-25446
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: qa
> Affects Versions: 4.5.2.AM2
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Blocker
> Labels: jenkins
> Fix For: 4.6.0.AM1, 4.6.x
>
>
> During jenkins job execution slaves is disconnected with exception
> {code}
> 19:09:27 19:09:27.096 DEBUG [WorkbenchTestable][AbstractWait] Waiting until shell matching Matcher matching when all matchers match: [Matcher matching widget which text matches: "Problem Occured"] is available....
> 19:09:32 FATAL: command execution failed
> 19:09:32 java.io.IOException: Backing channel 'Channel to /10.8.247.148' is disconnected.
> 19:09:32 at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:191)
> 19:09:32 at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:256)
> 19:09:32 at com.sun.proxy.$Proxy68.isAlive(Unknown Source)
> 19:09:32 at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1043)
> 19:09:32 at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1035)
> 19:09:32 at hudson.Launcher$ProcStarter.join(Launcher.java:399)
> 19:09:32 at hudson.tasks.Maven.perform(Maven.java:367)
> 19:09:32 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
> 19:09:32 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)
> 19:09:32 at hudson.model.Build$BuildExecution.build(Build.java:205)
> 19:09:32 at hudson.model.Build$BuildExecution.doRun(Build.java:162)
> 19:09:32 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
> 19:09:32 at hudson.model.Run.execute(Run.java:1728)
> 19:09:32 at hudson.matrix.MatrixRun.run(MatrixRun.java:146)
> 19:09:32 at hudson.model.ResourceController.execute(ResourceController.java:98)
> 19:09:32 at hudson.model.Executor.run(Executor.java:404)
> 19:09:32 Caused by: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@5af9151e[name=Channel to /10.8.247.148]
> 19:09:32 at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:210)
> 19:09:32 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:635)
> 19:09:32 at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
> 19:09:32 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> 19:09:32 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 19:09:32 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 19:09:32 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 19:09:32 at java.lang.Thread.run(Thread.java:748)
> 19:09:32 Caused by: java.io.IOException: Connection reset by peer
> 19:09:32 at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
> 19:09:32 at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
> 19:09:32 at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
> 19:09:32 at sun.nio.ch.IOUtil.read(IOUtil.java:197)
> 19:09:32 at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
> 19:09:32 at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:142)
> 19:09:32 at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:359)
> 19:09:32 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:564)
> 19:09:32 ... 6 more
> 19:09:32 Build step 'Invoke top-level Maven targets' marked build as failure
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25446) Windows/Mac slave gets disconnected during job execution
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25446?page=com.atlassian.jira.plugi... ]
Ondrej Dockal reassigned JBIDE-25446:
-------------------------------------
Assignee: Ondrej Dockal (was: Pavol Srna)
> Windows/Mac slave gets disconnected during job execution
> --------------------------------------------------------
>
> Key: JBIDE-25446
> URL: https://issues.jboss.org/browse/JBIDE-25446
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: qa
> Affects Versions: 4.5.2.AM2
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Blocker
> Labels: jenkins
> Fix For: 4.6.0.AM1, 4.6.x
>
>
> During jenkins job execution slaves is disconnected with exception
> {code}
> 19:09:27 19:09:27.096 DEBUG [WorkbenchTestable][AbstractWait] Waiting until shell matching Matcher matching when all matchers match: [Matcher matching widget which text matches: "Problem Occured"] is available....
> 19:09:32 FATAL: command execution failed
> 19:09:32 java.io.IOException: Backing channel 'Channel to /10.8.247.148' is disconnected.
> 19:09:32 at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:191)
> 19:09:32 at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:256)
> 19:09:32 at com.sun.proxy.$Proxy68.isAlive(Unknown Source)
> 19:09:32 at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1043)
> 19:09:32 at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1035)
> 19:09:32 at hudson.Launcher$ProcStarter.join(Launcher.java:399)
> 19:09:32 at hudson.tasks.Maven.perform(Maven.java:367)
> 19:09:32 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
> 19:09:32 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)
> 19:09:32 at hudson.model.Build$BuildExecution.build(Build.java:205)
> 19:09:32 at hudson.model.Build$BuildExecution.doRun(Build.java:162)
> 19:09:32 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
> 19:09:32 at hudson.model.Run.execute(Run.java:1728)
> 19:09:32 at hudson.matrix.MatrixRun.run(MatrixRun.java:146)
> 19:09:32 at hudson.model.ResourceController.execute(ResourceController.java:98)
> 19:09:32 at hudson.model.Executor.run(Executor.java:404)
> 19:09:32 Caused by: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@5af9151e[name=Channel to /10.8.247.148]
> 19:09:32 at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:210)
> 19:09:32 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:635)
> 19:09:32 at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
> 19:09:32 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> 19:09:32 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 19:09:32 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 19:09:32 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 19:09:32 at java.lang.Thread.run(Thread.java:748)
> 19:09:32 Caused by: java.io.IOException: Connection reset by peer
> 19:09:32 at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
> 19:09:32 at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
> 19:09:32 at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
> 19:09:32 at sun.nio.ch.IOUtil.read(IOUtil.java:197)
> 19:09:32 at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
> 19:09:32 at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:142)
> 19:09:32 at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:359)
> 19:09:32 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:564)
> 19:09:32 ... 6 more
> 19:09:32 Build step 'Invoke top-level Maven targets' marked build as failure
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months