[JBoss JIRA] (JBIDE-26893) Create universal template and label that would accommodate different rhel needed by interop testing team
by Ondrej Dockal (Jira)
Ondrej Dockal created JBIDE-26893:
-------------------------------------
Summary: Create universal template and label that would accommodate different rhel needed by interop testing team
Key: JBIDE-26893
URL: https://issues.jboss.org/browse/JBIDE-26893
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: integration-tests, qa
Affects Versions: 4.13.0.Final
Reporter: Ondrej Dockal
Assignee: Ondrej Dockal
Fix For: 4.14.x
We would like to use universal label that would cover different rhel versions that are required by interop testing. The idea is that we will keep one label for interop testing slave: rhel-interop, which would have used image: rhel-interop-snapshot that would have actually needed rhel version to test. During provisioning we will replace snapshot with proper rhel. This way we can keep one label and do not need to change interop test job label all the time via PR in cci-config repo.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (JBIDE-26869) CRC server adapter: OpenShift connection that is created is unusable at times
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26869?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26869:
-------------------------------
Sprint: devex #173 Oct 2019, devex #174 Oct 2019 (was: devex #173 Oct 2019)
> CRC server adapter: OpenShift connection that is created is unusable at times
> -----------------------------------------------------------------------------
>
> Key: JBIDE-26869
> URL: https://issues.jboss.org/browse/JBIDE-26869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.13.0.AM1
> Environment: CRC Beta5
> Reporter: André Dietisheim
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.13.0.Final
>
> Attachments: crc-connection-error.mp4, start-crc-error-openshift-conn.mp4
>
>
> *Steps* - not reproducibe at 100%, happens from time to time:
> # ASSERT: have ~/.crc folder killed
> # EXEC: create new CRC server adapter & Start it
> # ASSERT: OpenShift connection is created
> *Result:*
> Connection fails to authorize, reports that it cannot access resources using system:anonymous. Refreshing the connection doesn't help, so it's apparently not a timing issue (ex. creating the connection before the cluster is fully up and running)
> {code}
> com.openshift.restclient.authorization.ResourceForbiddenException: forbidden: User "system:anonymous" cannot get path "/oauth/authorize" forbidden: User "system:anonymous" cannot get path "/oauth/authorize"
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:111)
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:66)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:112)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:87)
> at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.kt:184)
> at okhttp3.RealCall.execute(RealCall.kt:66)
> at com.openshift.internal.restclient.okhttp.OpenShiftAuthenticator.tryAuth(OpenShiftAuthenticator.java:109)
> at com.openshift.internal.restclient.okhttp.OpenShiftAuthenticator.authenticate(OpenShiftAuthenticator.java:62)
> at okhttp3.internal.http.RetryAndFollowUpInterceptor.followUpRequest(RetryAndFollowUpInterceptor.kt:213)
> at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:102)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:112)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:87)
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:55)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:112)
> at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:87)
> at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.kt:184)
> at okhttp3.RealCall.execute(RealCall.kt:66)
> at com.openshift.internal.restclient.DefaultClient.request(DefaultClient.java:315)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:307)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:275)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:243)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:226)
> at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:423)
> at com.openshift.internal.restclient.authorization.AuthorizationContext.isAuthorized(AuthorizationContext.java:63)
> at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:237)
> at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:226)
> at org.jboss.tools.openshift.internal.crc.server.core.listeners.ConfigureCRCFrameworksListener.configureOpenshift(ConfigureCRCFrameworksListener.java:102)
> at org.jboss.tools.openshift.internal.crc.server.core.listeners.ConfigureCRCFrameworksListener.configureFrameworks(ConfigureCRCFrameworksListener.java:73)
> at org.jboss.tools.openshift.internal.crc.server.core.listeners.ConfigureCRCFrameworksListener$1.run(ConfigureCRCFrameworksListener.java:66)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (JBIDE-26787) Several tests in examples.wildfly.itests are failing due to "Exception during sync execution in UI thread"
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26787?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26787:
-------------------------------
Sprint: devex #172 Sep 2019, devex #173 Oct 2019, devex #174 Oct 2019 (was: devex #172 Sep 2019, devex #173 Oct 2019)
> Several tests in examples.wildfly.itests are failing due to "Exception during sync execution in UI thread"
> -----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26787
> URL: https://issues.jboss.org/browse/JBIDE-26787
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-tests, project-examples
> Affects Versions: 4.13.0.AM1
> Environment: All, tests are failing sporadically.
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Major
>
> Several tests in examples.wildfly.itests are failing due to "Exception during sync execution in UI thread"
> h2. *Jenkins:*
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples...
> h2. *Stack Trace:*
> org.eclipse.reddeer.common.exception.RedDeerException: Exception during sync execution in UI thread
> at org.jboss.tools.examples.ui.bot.test.integration.WildFlyImportQuickstartsTest.quickstartTest(WildFlyImportQuickstartsTest.java:62)
> Caused by: org.eclipse.swt.SWTException: Widget is disposed
> h2. *Standard Error:*
> org.eclipse.reddeer.common.exception.RedDeerException: Exception during sync execution in UI thread
> at org.eclipse.reddeer.common.util.Display.handleErrorOccured(Display.java:112)
> at org.eclipse.reddeer.common.util.Display.syncExec(Display.java:84)
> at org.eclipse.reddeer.core.handler.TreeItemHandler.getText(TreeItemHandler.java:68)
> at org.eclipse.reddeer.swt.impl.tree.AbstractTreeItem.getCell(AbstractTreeItem.java:77)
> at org.eclipse.reddeer.eclipse.ui.problems.Problem.getCell(Problem.java:68)
> at org.eclipse.reddeer.eclipse.ui.markers.AbstractMarker.getDescription(AbstractMarker.java:43)
> at org.jboss.tools.central.reddeer.api.ExamplesOperator.getAllWarnings(ExamplesOperator.java:225)
> at org.jboss.tools.examples.ui.bot.test.integration.AbstractImportQuickstartsTest.checkForWarnings(AbstractImportQuickstartsTest.java:375)
> at org.jboss.tools.examples.ui.bot.test.integration.AbstractImportQuickstartsTest.runQuickstarts(AbstractImportQuickstartsTest.java:283)
> at org.jboss.tools.examples.ui.bot.test.integration.WildFlyImportQuickstartsTest.quickstartTest(WildFlyImportQuickstartsTest.java:62)
> at jdk.internal.reflect.GeneratedMethodAccessor185.invoke(Unknown Source)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>
> ...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months
[JBoss JIRA] (JBIDE-26750) Update CDI.itests to run on java 11 and add some parameters to the pom.xml
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26750?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26750:
-------------------------------
Sprint: devex #172 Sep 2019, devex #173 Oct 2019, devex #174 Oct 2019 (was: devex #172 Sep 2019, devex #173 Oct 2019)
> Update CDI.itests to run on java 11 and add some parameters to the pom.xml
> --------------------------------------------------------------------------
>
> Key: JBIDE-26750
> URL: https://issues.jboss.org/browse/JBIDE-26750
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: cdi
> Affects Versions: 4.13.0.AM1
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Major
> Fix For: 4.13.0.Final
>
>
> *Description of the task from [~odockal]:*
> As I said some time ago, would be awesome to also have test project running on Java 11 in case that test are running on machine with jdk 11. Also, I can see that this condition repeats in every class, do you dare to extract it somewhere else and just call in @requirementResctriction annotated method?
> Let's put it into some utility class, that's an easiest solution.
> Update:
> I can image that server family and version would be parametrized in pom. One could have parameter ie. server.family and server.version and so any update to server and its version could happen in one place at once.
> And you can run test for both server eap and wildfly driven by param in jenkins.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 8 months