[JBoss JIRA] (JBIDE-25276) intermittent test failures in webservices
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25276?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-25276:
-------------------------------
Fix Version/s: 4.5.2.AM3
(was: 4.5.2.AM2)
> intermittent test failures in webservices
> -----------------------------------------
>
> Key: JBIDE-25276
> URL: https://issues.jboss.org/browse/JBIDE-25276
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 4.5.2.AM3
>
>
> Various tests are failing intermittently.
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> * org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testClientCodeGenerationCommand
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> * org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> * org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> * All Failed Tests
> Test Name
> Duration
> Age
> org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest.testDeployResult 12 sec 1
> org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest.testDeployResult 12 sec 1
> org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest.testDeployResult 37 sec 1
> org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testInitialClientCommand 0.65 sec 1
> org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testClientCodeGenerationCommand 0.6 sec 1
> org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testRemoveClientJarsCommand 0.59 sec 1
> org.jboss.tools.ws.creation.core.test.command.JBossWSMergeWebXMLCommandTest.testMergeWebXMLCommand 20 min 1
> org.jboss.tools.ws.jaxrs.core.internal.metamodel.indexation.JaxrsElementsIndexationDelegateTestCase.shouldIndexAndRetrieveMultipleEndpointsFromJavaApplication 0.1 sec 1
> org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication 0.67 sec 2
> Can these be fixed or if not, disabled, so that we can consistently get green builds?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25276) intermittent test failures in webservices
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25276?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-25276:
-------------------------------
Sprint: devex #139 October 2017, devex #142 December 2017 (was: devex #139 October 2017, devex #141 December 2017)
> intermittent test failures in webservices
> -----------------------------------------
>
> Key: JBIDE-25276
> URL: https://issues.jboss.org/browse/JBIDE-25276
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 4.5.2.AM3
>
>
> Various tests are failing intermittently.
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> * org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testClientCodeGenerationCommand
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> * org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> * org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> * All Failed Tests
> Test Name
> Duration
> Age
> org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest.testDeployResult 12 sec 1
> org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest.testDeployResult 12 sec 1
> org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest.testDeployResult 37 sec 1
> org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testInitialClientCommand 0.65 sec 1
> org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testClientCodeGenerationCommand 0.6 sec 1
> org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testRemoveClientJarsCommand 0.59 sec 1
> org.jboss.tools.ws.creation.core.test.command.JBossWSMergeWebXMLCommandTest.testMergeWebXMLCommand 20 min 1
> org.jboss.tools.ws.jaxrs.core.internal.metamodel.indexation.JaxrsElementsIndexationDelegateTestCase.shouldIndexAndRetrieveMultipleEndpointsFromJavaApplication 0.1 sec 1
> org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication 0.67 sec 2
> Can these be fixed or if not, disabled, so that we can consistently get green builds?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25276) intermittent test failures in webservices
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25276?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-25276:
------------------------------------
[checkUnresolvedIssues.py] Slip to fixversion = *4.5.2.AM3* and sprint = *devex #142 December 2017*
> intermittent test failures in webservices
> -----------------------------------------
>
> Key: JBIDE-25276
> URL: https://issues.jboss.org/browse/JBIDE-25276
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 4.5.2.AM3
>
>
> Various tests are failing intermittently.
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> * org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testClientCodeGenerationCommand
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> * org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> * org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> * All Failed Tests
> Test Name
> Duration
> Age
> org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest.testDeployResult 12 sec 1
> org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest.testDeployResult 12 sec 1
> org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest.testDeployResult 37 sec 1
> org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testInitialClientCommand 0.65 sec 1
> org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testClientCodeGenerationCommand 0.6 sec 1
> org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testRemoveClientJarsCommand 0.59 sec 1
> org.jboss.tools.ws.creation.core.test.command.JBossWSMergeWebXMLCommandTest.testMergeWebXMLCommand 20 min 1
> org.jboss.tools.ws.jaxrs.core.internal.metamodel.indexation.JaxrsElementsIndexationDelegateTestCase.shouldIndexAndRetrieveMultipleEndpointsFromJavaApplication 0.1 sec 1
> org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication 0.67 sec 2
> Can these be fixed or if not, disabled, so that we can consistently get green builds?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBDS-4617) [rpm] NoClassDefFoundError: org/apache/http/client/cache/HttpCacheStorage
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4617?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4617:
-----------------------------
Fix Version/s: 11.2.0.AM3
> [rpm] NoClassDefFoundError: org/apache/http/client/cache/HttpCacheStorage
> -------------------------------------------------------------------------
>
> Key: JBDS-4617
> URL: https://issues.jboss.org/browse/JBDS-4617
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central, central-update, cordovasim, rpm
> Affects Versions: 11.1.0.GA
> Environment: RHEL7, devtools 2.1 \[1\] and DevStudio 11.1-0.20171026.1132.el7 installed from snapshot repository \[2\].
> \[1\] http://brewweb.engineering.redhat.com/brewroot/repos/devtools-2.1-rh-ecli...
> \[2\] https://devstudio.redhat.com/11/snapshots/rpms/11/x86_64/
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 11.2.0.AM3, 11.x
>
> Attachments: Error_dialog.png, hma-wizard-stuck.png, rh-eclipse47-devstudio11.1-0.20171026.1132.el7.log.20171030-1600_strict.txt
>
>
> I got this error when I tried to use "Hybrid Mobile (Cordova) Application Project" wizard.
> {code}
> !ENTRY org.eclipse.jface 4 2 2017-10-30 16:41:56.780
> !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface".
> !STACK 0
> java.lang.NoClassDefFoundError: org/apache/http/client/cache/HttpCacheStorage
> at org.eclipse.thym.core.engine.internal.cordova.NpmBasedEngineRepoProvider.getPlatformEngines(NpmBasedEngineRepoProvider.java:61)
> at org.eclipse.thym.core.engine.internal.cordova.NpmBasedEngineRepoProvider.getEngines(NpmBasedEngineRepoProvider.java:51)
> at org.eclipse.thym.core.engine.internal.cordova.CordovaEngineProvider.getDownloadableEngines(CordovaEngineProvider.java:169)
> at org.eclipse.thym.core.engine.internal.cordova.CordovaEngineProvider.initEngineList(CordovaEngineProvider.java:92)
> at org.eclipse.thym.core.engine.internal.cordova.CordovaEngineProvider.getAvailableEngines(CordovaEngineProvider.java:108)
> at org.eclipse.thym.ui.internal.engine.AvailableCordovaEnginesSection.updateAvailableEngines(AvailableCordovaEnginesSection.java:386)
> at org.eclipse.thym.ui.internal.engine.AvailableCordovaEnginesSection.createControl(AvailableCordovaEnginesSection.java:365)
> at org.eclipse.thym.ui.wizard.project.EngineConfigurationPage.createControl(EngineConfigurationPage.java:52)
> at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:176)
> at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:688)
> at org.eclipse.jface.wizard.WizardDialog.setWizard(WizardDialog.java:1128)
> at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1181)
> at org.eclipse.jface.wizard.WizardDialog.lambda$3(WizardDialog.java:1169)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1169)
> at org.eclipse.ui.internal.dialogs.NewWizardSelectionPage.advanceToNextPageOrFinish(NewWizardSelectionPage.java:71)
> at org.eclipse.ui.internal.dialogs.NewWizardNewPage.lambda$0(NewWizardNewPage.java:348)
> at org.eclipse.jface.viewers.StructuredViewer$1.run(StructuredViewer.java:831)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil.lambda$0(JFaceUtil.java:44)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.viewers.StructuredViewer.fireDoubleClick(StructuredViewer.java:828)
> at org.eclipse.jface.viewers.AbstractTreeViewer.handleDoubleSelect(AbstractTreeViewer.java:1459)
> at org.eclipse.jface.viewers.StructuredViewer$4.widgetDefaultSelected(StructuredViewer.java:1258)
> at org.eclipse.jface.util.OpenStrategy.fireDefaultSelectionEvent(OpenStrategy.java:249)
> at org.eclipse.jface.util.OpenStrategy.access$0(OpenStrategy.java:247)
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:306)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5268)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1348)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4522)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4107)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:291)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:92)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:305)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:239)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:487)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:390)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:151)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5268)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1348)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4522)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4107)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
> Caused by: java.lang.ClassNotFoundException: org.apache.http.client.cache.HttpCacheStorage cannot be found by org.eclipse.thym.core_2.1.0.201710130741
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:484)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:395)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:387)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 81 more
> !ENTRY org.eclipse.thym.ui 2 0 2017-10-30 16:41:58.735
> !MESSAGE Unable to determine if cordova is available
> !STACK 0
> java.lang.IllegalArgumentException: invalid version "You have been opted out of telemetry. To change this, run: cordova telemetry on.
> 6.4.0": non-numeric "You have been opted out of telemetry"
> at org.osgi.framework.Version.parseInt(Version.java:170)
> at org.osgi.framework.Version.<init>(Version.java:126)
> at org.osgi.framework.Version.valueOf(Version.java:257)
> at org.osgi.framework.Version.parseVersion(Version.java:228)
> at org.eclipse.thym.ui.wizard.project.WizardNewHybridProjectCreationPage$CordovaIsAvailableJob.run(WizardNewHybridProjectCreationPage.java:237)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: java.lang.NumberFormatException: For input string: "You have been opted out of telemetry"
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:580)
> at java.lang.Integer.parseInt(Integer.java:615)
> at org.osgi.framework.Version.parseInt(Version.java:168)
> ... 5 more
> {code}
> Please see also Steps to Reproduce.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 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:
----------------------------------
Fix Version/s: 4.5.x
> 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.5.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)
8 years, 3 months
[JBoss JIRA] (JBIDE-25455) JBoss Tools marketplace listing includes org.eclipse features
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25455?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-25455 at 12/12/17 10:50 AM:
---------------------------------------------------------------
Here's the list of org.eclipse feature currently in the jbosstools markeplace entry [1].
!jbosstools-eclipse-plugins-marketplace.png|thumbnail!
[1] https://marketplace.eclipse.org/content/jboss-tools/edit
I would imagine we should remove all of them? Or maybe keep buildship, since it's included in the JBT update site [2], [3]?
[2] http://download.jboss.org/jbosstools/static/oxygen/stable/updates/core/4....
[3] http://download.jboss.org/jbosstools/static/oxygen/stable/updates/core/4....
Note that Buildship was added to JBT and devstudio as an OOTB install via JBDS-3510, back on May 31, 2017.
was (Author: nickboldt):
Here's the list of org.eclipse feature currently in the jbosstools markeplace entry [1].
!jbosstools-eclipse-plugins-marketplace.png|thumbnail!
[1] https://marketplace.eclipse.org/content/jboss-tools/edit
I would imagine we should remove all of them? Or maybe keep buildship, since for some reason it's included in the JBT update site [2], [3]?
[2] http://download.jboss.org/jbosstools/static/oxygen/stable/updates/core/4....
[3] http://download.jboss.org/jbosstools/static/oxygen/stable/updates/core/4....
Note that Buildship was added to JBT and devstudio as an OOTB install via JBDS-3510, back on May 31, 2017.
> JBoss Tools marketplace listing includes org.eclipse features
> -------------------------------------------------------------
>
> Key: JBIDE-25455
> URL: https://issues.jboss.org/browse/JBIDE-25455
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: marketplace
> Affects Versions: 4.5.1.Final
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Fix For: 4.5.2.Final
>
> Attachments: jbosstools-eclipse-plugins-marketplace.png
>
>
> Someone added org.eclipse.buildship and org.eclipse.wst.* features to the Marketplace listing as optional-selected features.
> Shouldn't these be installed via requirements from JBT features, and therefore not needed on the site?
> The list of sanctioned features in the CoreTools category on the JBT site is here:
> http://download.jboss.org/jbosstools/static/oxygen/stable/updates/core/4....
> So... why did the other features get added? And if they SHOULD be there, they should also be added to the JBT site too, for consistency. Right?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months