[JBoss JIRA] (JBIDE-25276) intermittent test failures in webservices
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25276?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25276:
-------------------------------
Sprint: devex #139 October 2017, devex #143 January 2018 (was: devex #139 October 2017, devex #143 January 2018, devex #145 February 2018)
> 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.x
>
> Attachments: ws-intermittent-test-failures.png
>
>
> 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, 1 month
[JBoss JIRA] (JBIDE-25696) Deadlock when running JBoss Tools Project Validator on startup
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25696?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25696:
-------------------------------
Story Points: 10
> Deadlock when running JBoss Tools Project Validator on startup
> --------------------------------------------------------------
>
> Key: JBIDE-25696
> URL: https://issues.jboss.org/browse/JBIDE-25696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi, common, jst
> Environment: JBoss Developer Studio 11.2.0.GA, Windows 10
> Reporter: Vsevolod Golovanov
> Assignee: Jeff MAURY
> Priority: Blocker
> Fix For: 4.5.3.AM2
>
> Attachments: lockedup.png, threaddump-1518088511239.tdump
>
>
> The workspace is one EAR project, a couple dozen EJBs, 2 WARs, a couple dozen JAR webfragments (deployed inside the WARs), some misc projects - 67 projects alltogether.
> When opening it sometimes locks up completely - UI is not responding, process CPU is at 0%.
> Here's what it looks like: !lockedup.png|thumbnail!
> This time I just opened the Problems view and clicked Markers, which never opened. But I don't think this isn't necessary, pretty sure it sometimes hangs without clicking anything at all.
> It always shows JBoss Tools Project Validator in the Progress view when this happens.
> VisualVM reports a deadlock, seems to be JBoss Tools Validator related: [^threaddump-1518088511239.tdump]
> I think this used to happen with JBDS10 too, but I don't know for sure, because I don't have the threaddumps.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (JBIDE-25276) intermittent test failures in webservices
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25276?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25276:
-------------------------------
Fix Version/s: (was: 4.5.3.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.x
>
> Attachments: ws-intermittent-test-failures.png
>
>
> 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, 1 month
[JBoss JIRA] (JBIDE-25669) Unexpected JAX-RS validation error for Feature
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25669?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25669:
-------------------------------
Story Points: 10
> Unexpected JAX-RS validation error for Feature
> ----------------------------------------------
>
> Key: JBIDE-25669
> URL: https://issues.jboss.org/browse/JBIDE-25669
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.5.2.Final
> Reporter: Cody Lerum
> Assignee: Jeff MAURY
> Labels: jax-rs, respin-a
> Fix For: 4.5.3.AM2
>
>
> We are using JAX-RS client filters in our project. One of the classes looks like this:
> ...
> import java.io.IOException;
> import javax.ws.rs.client.ClientRequestContext;
> import javax.ws.rs.client.ClientRequestFilter;
> import javax.ws.rs.ext.Provider;
> ...
> @Provider
> public class ClientFilter implements ClientRequestFilter
> {
> ...
> }
> The class is part of a Dynamic Web Project with JAX-RS support turned on.
> The combination of @Provider and either of the ClientRequestFilter or ClientRequestFilter appears to confuse the JAX-RS validator which produces the following error:
> The Provider must implement at least one of the following interfaces: javax.ws.rs.ext.MessageBodyReader, javax.ws.rs.ext.MessageBodyWriter, javax.ws.rs.ext.ExceptionMapper, javax.ws.rs.ext.ReaderInterceptor, javax.ws.rs.ext.WriterInterceptor, javax.ws.rs.container.ContainerRequestFilter, javax.ws.rs.container.ContainerResponseFilter or javax.ws.rs.ext.ContextResolver.
> I suspect the validator needs to be enhanced to also accept the two client filter interfaces when checking the @Provider annotation?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (JBIDE-25733) Tests failures in OpenShift for Java9
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-25733:
----------------------------------
Summary: Tests failures in OpenShift for Java9
Key: JBIDE-25733
URL: https://issues.jboss.org/browse/JBIDE-25733
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.5.3.AM1
Reporter: Jeff MAURY
Assignee: Dmitrii Bocharov
Fix For: 4.5.3.AM2
Some unit tests are failing because of the Powermock dependency
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month