February 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2262) [DMN Designer] DRD Grid Column width is not preserved

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-2262?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-2262: ------------------------------------- [~manstis] [~danielezonca] I am sorry for my wrong assumption. Thank you for an explanation. > [DMN Designer] DRD Grid Column width is not preserved > ----------------------------------------------------- > > Key: DROOLS-2262 > URL: https://issues.jboss.org/browse/DROOLS-2262 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > DND Grid Column don't preserve the width. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-508) Automate - Services List 'Error Rate' field

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-508?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan deleted SWSQE-508: --------------------------------- > Automate - Services List 'Error Rate' field > ------------------------------------------- > > Key: SWSQE-508 > URL: https://issues.jboss.org/browse/SWSQE-508 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Michael Foley > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-505) Automate - Workloads List Error Rate field

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-505?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan deleted SWSQE-505: --------------------------------- > Automate - Workloads List Error Rate field > ------------------------------------------ > > Key: SWSQE-505 > URL: https://issues.jboss.org/browse/SWSQE-505 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Michael Foley > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-526) UI Tests - Make version compatible to run for TP

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-526?page=com.atlassian.jira.plugin.... ] Filip Brychta updated SWSQE-526: -------------------------------- Sprint: Kiali Sprint #14, Kiali Sprint #17, Kiali Sprint #18 (was: Kiali Sprint #14, Kiali Sprint #17) > UI Tests - Make version compatible to run for TP > ------------------------------------------------ > > Key: SWSQE-526 > URL: https://issues.jboss.org/browse/SWSQE-526 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Filip Brychta > Priority: Major > > Currently when Kiali is released with older version than latest master, UI tests is not possible to run: > 1. UI tests are not tagged. > 2. Kiali REST Client is always latest on jenkins slaves. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-587) Python broken in jenkins-slave-kiali-ui-tests-python3

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-587?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-587. --------------------------------- Resolution: Done Fixed python bin to point to python2, python3 points to python3.6. Pip and pytest are from python3. Also consolidated jenkins-slave-kiali-ui-tests and jenkins-slave-kiali-ui-tests-python3 to one and removed old jenkins job run-python-ui-tests. The same problem was in jenkins-slave-kiali-rest-tests. Update slave labels and doc https://mojo.redhat.com/docs/DOC-1168333 > Python broken in jenkins-slave-kiali-ui-tests-python3 > ----------------------------------------------------- > > Key: SWSQE-587 > URL: https://issues.jboss.org/browse/SWSQE-587 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > > sh-4.2$ yum > sh: /usr/bin/yum: /usr/bin/python: bad interpreter: No such file or directory > sh-4.2$ python > sh: python: command not found > sh-4.2$ > Check other slaves as well -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-554) Add missing Openshift API calls

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-554?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan resolved SWSQE-554. ---------------------------------- Resolution: Done > Add missing Openshift API calls > ------------------------------- > > Key: SWSQE-554 > URL: https://issues.jboss.org/browse/SWSQE-554 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > > Currently there are several areas in UI tests that do not have call to Openshift API for data comparison. > 1. Figure out which calls are missing to Openshift. > 2. Create API call. > 3. Create assertions on that results to compare with UI data. > 4. PR per area (API call). -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-554) Add missing Openshift API calls

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-554?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan updated SWSQE-554: --------------------------------- Sprint: Kiali Sprint #16, Kiali Sprint #17 (was: Kiali Sprint #16, Kiali Sprint #17, Kiali Sprint #18) > Add missing Openshift API calls > ------------------------------- > > Key: SWSQE-554 > URL: https://issues.jboss.org/browse/SWSQE-554 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > > Currently there are several areas in UI tests that do not have call to Openshift API for data comparison. > 1. Figure out which calls are missing to Openshift. > 2. Create API call. > 3. Create assertions on that results to compare with UI data. > 4. PR per area (API call). -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-554) Add missing Openshift API calls

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-554?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan updated SWSQE-554: --------------------------------- Sprint: Kiali Sprint #16, Kiali Sprint #17, Kiali Sprint #18 (was: Kiali Sprint #16, Kiali Sprint #17, Kiali Sprint #18) > Add missing Openshift API calls > ------------------------------- > > Key: SWSQE-554 > URL: https://issues.jboss.org/browse/SWSQE-554 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > > Currently there are several areas in UI tests that do not have call to Openshift API for data comparison. > 1. Figure out which calls are missing to Openshift. > 2. Create API call. > 3. Create assertions on that results to compare with UI data. > 4. PR per area (API call). -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-554) Add missing Openshift API calls

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-554?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan updated SWSQE-554: --------------------------------- Sprint: Kiali Sprint #16, Kiali Sprint #17, Kiali Sprint #18 (was: Kiali Sprint #16, Kiali Sprint #17) > Add missing Openshift API calls > ------------------------------- > > Key: SWSQE-554 > URL: https://issues.jboss.org/browse/SWSQE-554 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > > Currently there are several areas in UI tests that do not have call to Openshift API for data comparison. > 1. Figure out which calls are missing to Openshift. > 2. Create API call. > 3. Create assertions on that results to compare with UI data. > 4. PR per area (API call). -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11670) Intermittent failures in EJBClientXidTransactionTestCase.testServerSuspension

by Yeray Borges (Jira)

[ https://issues.jboss.org/browse/WFLY-11670?page=com.atlassian.jira.plugin... ] Yeray Borges commented on WFLY-11670: ------------------------------------- [~brian.stansberry] Yes, your suspicions are correct. Error trace is the same. Checking that one I realized today that [~flavia.rainone] had already created a fix for this sort of errors. I forgot to review the PR queue on qildfly-transaction-client before creating mine. I fixed as I could the jira issues and PRs since they were duplicated. What we need now to get it fixed in wildfly is a merging of WTC-60 in 1.1 branch and a component upgrade of wildly-transaction-client to 1.1.3.Final > Intermittent failures in EJBClientXidTransactionTestCase.testServerSuspension > ----------------------------------------------------------------------------- > > Key: WFLY-11670 > URL: https://issues.jboss.org/browse/WFLY-11670 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Brian Stansberry > Assignee: Yeray Borges > Priority: Major > > Test started failing fairly frequently on Jan 11: > https://ci.wildfly.org/project.html?projectId=WildFlyCore_PullRequest&bui... > https://ci.wildfly.org/project.html?projectId=WF&buildTypeId=&tab=testDet... > Perhaps that was related to https://github.com/wildfly/wildfly/pull/11913 which at a glance was the PR being tested in the first failure and may have been merged that day. So, [~yersan] I'm assigning to you to have a quick look. > I'll @Ignore the test. > For the record, this is the relevant error trace logged by the failed tests: > {noformat} > multinode.transaction.ClientEjb.testSameTransactionEachCall() throws java.rmi.RemoteException,javax.transaction.SystemException,javax.transaction.NotSupportedException,javax.naming.NamingException: javax.ejb.EJBException: EJBCLIENT000082: Cannot outflow the remote transaction "Local transaction (delegate=TransactionImple < ac, BasicAction: 0:ffff7f000101:-39b44114:5c59a6ad:10 status: ActionStatus.RUNNING >, owner=Local transaction context for provider JBoss JTA transaction provider)" as its timeout elapsed > at org.jboss.ejb.protocol.remote.EJBClientChannel.processInvocation(EJBClientChannel.java:471) > at org.jboss.ejb.protocol.remote.RemoteEJBReceiver$1.lambda$handleDone$0(RemoteEJBReceiver.java:91) > at org.xnio.FinishedIoFuture.addNotifier(FinishedIoFuture.java:79) > at org.jboss.ejb.protocol.remote.RemoteEJBReceiver$1.handleDone(RemoteEJBReceiver.java:76) > at org.jboss.ejb.protocol.remote.RemoteEJBReceiver$1.handleDone(RemoteEJBReceiver.java:74) > at org.xnio.IoFuture$HandlingNotifier.notify(IoFuture.java:208) > at org.xnio.AbstractIoFuture$NotifierRunnable.run(AbstractIoFuture.java:720) > at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:949) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) > at java.lang.Thread.run(Thread.java:748) > Caused by: javax.transaction.SystemException: EJBCLIENT000082: Cannot outflow the remote transaction "Local transaction (delegate=TransactionImple < ac, BasicAction: 0:ffff7f000101:-39b44114:5c59a6ad:10 status: ActionStatus.RUNNING >, owner=Local transaction context for provider JBoss JTA transaction provider)" as its timeout elapsed > at org.jboss.ejb.protocol.remote.EJBClientChannel.writeTransaction(EJBClientChannel.java:581) > at org.jboss.ejb.protocol.remote.EJBClientChannel.processInvocation(EJBClientChannel.java:367) > ... 12 more > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2019