July 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-356) Improve jenkins node provisioning scheduler

by Filip Brychta (JIRA)

Filip Brychta created SWSQE-356: ----------------------------------- Summary: Improve jenkins node provisioning scheduler Key: SWSQE-356 URL: https://issues.jboss.org/browse/SWSQE-356 Project: Kiali QE Issue Type: Sub-task Reporter: Filip Brychta Assignee: Filip Brychta When starting more concurrent jobs which are using the same slave labels the jobs are scheduled but stays in the queue for long time before new slave is provisioned. It's described here why - https://support.cloudbees.com/hc/en-us/articles/115000060512-New-Shared-A... I already tried some tuning of those parameters but it still stays long in the queue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-355) Tune zalenium to be more stable for parallel execution

by Filip Brychta (JIRA)

Filip Brychta created SWSQE-355: ----------------------------------- Summary: Tune zalenium to be more stable for parallel execution Key: SWSQE-355 URL: https://issues.jboss.org/browse/SWSQE-355 Project: Kiali QE Issue Type: Sub-task Reporter: Filip Brychta Assignee: Filip Brychta There is lot of timeouts and other errors when starting more selenium containers in parallel. We need to tune zalenium to be more stable. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10607) Fix intermittent failures in RemoteEJBForwardingTestCases

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/WFLY-10607?page=com.atlassian.jira.plugin... ] Richard Achmatowicz edited comment on WFLY-10607 at 7/26/18 8:33 AM: --------------------------------------------------------------------- I have found out why the test was still failing. Upon looking at the test environment setup, it was observed that the two clusters {code} ejb-forwarder = {node-1, node-2} {code} and {code} ejb={node-3, node4} {code} were not forming correctly. Once the cluster setup was fixed, and with the above mentioned change to the synchronization interceptor, the test now passes. What was the problem with the test case setup and why were the clusters not forming correctly? The test case setup depends on several steps carried out in the testsuite/integration/clustering pom.xml file: * use a wildfly-maven-plugin execution to adjust the stack of the base distribution used in the test via clustering-all.cli * use a maven antrun-plugin execution to copy the distribution to the four server distributions wildfly-1, wildfly-2, wildfly-3, wildfly4 * use a maven-surefilre-plugin execution to run the 2 clusters test using the four servers which have been started with the default socket-binding multicast addresses (this by default causes the four nodes to all be members of the same cluster when started) * use a ServerSetupTask in the test case itself to further configure the four nodes so that they form two separate clusters suitable for the test It was noticed that the two clusters were not forming correctly. Upon further investigation using the management console, it was seen that the multicast addresses were correctly configured in each server's management interface, but that the actual multicast addresses used were not correct. This was traced to the following issue: https://issues.jboss.org/browse/WFCORE-3977. What was happening was that the ServerSetupTask was correctly making the changes via the management CLI, but because the servers were not put into reload-required, the changes were not taking effect and the clusters were not forming correctly. Forcing a reload of the servers causes the servers to configure correctly. With correctly configured server environment, plus the changes to the synchronization interceptor mentioned above, the tests now pass. was (Author: rachmato): I have found out why the test was still failing. Upon looking at the test environment setup, it was observed that the two clusters ejb-forwarder = {node-1, node-2} and ejb={node-3, node4} were not forming correctly. Once the cluster setup was fixed, and with the above mentioned change to the synchronization interceptor, the test now passes. What was the problem with the test case setup and why were the clusters not forming correctly? The test case setup depends on several steps carried out in the testsuite/integration/clustering pom.xml file: * use a wildfly-maven-plugin execution to adjust the stack of the base distribution used in the test via clustering-all.cli * use a maven antrun-plugin execution to copy the distribution to the four server distributions wildfly-1, wildfly-2, wildfly-3, wildfly4 * use a maven-surefilre-plugin execution to run the 2 clusters test using the four servers which have been started with the default socket-binding multicast addresses (this by default causes the four nodes to all be members of the same cluster when started) * use a ServerSetupTask in the test case itself to further configure the four nodes so that they form two sepaate clusters suitable for the test It was noticed that the two clusters were not forming correctly. Upon further investigation using the management console, it was seen that the multicast addresses were correctly configured in each server's management interface, but that the actual multicast addresses used were not correct. This was traced to the following issue: https://issues.jboss.org/browse/WFCORE-3977. What was happening was that the ServerSetupTask was correctly making the changes via the management CLI, but because the servers were not put into reload-required, the changes were not taking effect and the clusters were not forming correct. Forcing a reload of the servers causes the servers to configure correctly. With correctly configured server environment, pluse the changes to the synchronization interceptor mentioned above, the tests now pass. > Fix intermittent failures in RemoteEJBForwardingTestCases > --------------------------------------------------------- > > Key: WFLY-10607 > URL: https://issues.jboss.org/browse/WFLY-10607 > Project: WildFly > Issue Type: Bug > Components: EJB, Test Suite > Reporter: Petr Kremensky > Assignee: Richard Achmatowicz > > The tests were ignored by https://github.com/wildfly/wildfly/pull/10563/files -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-324) Routing issue with zalenium

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/SWSQE-324?page=com.atlassian.jira.plugin.... ] Filip Brychta commented on SWSQE-324: ------------------------------------- As a workaround on b20 I defined order of DNS in /etc/dnsmasq.d/origin-upstream-dns.conf (taken from bottom to top for some reason) and enabled strict-order in /etc/dnsmasq.conf which should force dnsmasq to try DNS in listed order. So far it's working fine without the 'Name or service not known' error. > Routing issue with zalenium > --------------------------- > > Key: SWSQE-324 > URL: https://issues.jboss.org/browse/SWSQE-324 > Project: Kiali QE > Issue Type: QE Task > Reporter: Jeeva Kandasamy > Assignee: Filip Brychta > > I see the following error(I guess it is routing error) weekly once, > ------ > http_conn_args = {}, host = 'zalenium.prod.os.jonqe.lab.eng.bos.redhat.com' > h = <httplib.HTTPConnection instance at 0x7f45e47c6c68> > err = gaierror(-2, 'Name or service not known') > ------ > Detailed report: http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/run-python-ui-te... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-324) Routing issue with zalenium

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/SWSQE-324?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-324. --------------------------------- Resolution: Done > Routing issue with zalenium > --------------------------- > > Key: SWSQE-324 > URL: https://issues.jboss.org/browse/SWSQE-324 > Project: Kiali QE > Issue Type: QE Task > Reporter: Jeeva Kandasamy > Assignee: Filip Brychta > > I see the following error(I guess it is routing error) weekly once, > ------ > http_conn_args = {}, host = 'zalenium.prod.os.jonqe.lab.eng.bos.redhat.com' > h = <httplib.HTTPConnection instance at 0x7f45e47c6c68> > err = gaierror(-2, 'Name or service not known') > ------ > Detailed report: http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/run-python-ui-te... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2786) Investigate and create a scenario simulation showcase

by Juraj Soltes (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2786?page=com.atlassian.jira.plugi... ] Juraj Soltes updated DROOLS-2786: --------------------------------- Tester: Juraj Soltes (was: Klara Kufova) > Investigate and create a scenario simulation showcase > ----------------------------------------------------- > > Key: DROOLS-2786 > URL: https://issues.jboss.org/browse/DROOLS-2786 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Labels: ScenarioSimulation > > Create a Scenario Simulation showcase project to be able to run Drools WB only with this asset -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10746) NullPointerException in ELFlash.get

by Bartosz Spyrko-Śmietanko (JIRA)

[ https://issues.jboss.org/browse/WFLY-10746?page=com.atlassian.jira.plugin... ] Bartosz Spyrko-Śmietanko edited comment on WFLY-10746 at 7/26/18 8:30 AM: -------------------------------------------------------------------------- https://java.net/jira/browse/JAVASERVERFACES-3621 is resolved in 2.3.5.SP1, but there's one more case where issue occurs: https://github.com/javaserverfaces/mojarra/issues/4379 > NullPointerException in ELFlash.get > ----------------------------------- > > Key: WFLY-10746 > URL: https://issues.jboss.org/browse/WFLY-10746 > Project: WildFly > Issue Type: Bug > Components: JSF > Environment: Red Hat JBoss Enterprise Application Platform 7.1.0 > Reporter: Bartosz Spyrko-Śmietanko > Assignee: Bartosz Spyrko-Śmietanko > > The following NPE happenes when calling ELFlash.get in EAP 7.1.0. > ~~~ > java.lang.NullPointerException > at com.sun.faces.context.flash.ELFlash.get(ELFlash.java:412) > ~~~ > The same issue was reported in: > Fixes https://java.net/jira/browse/JAVASERVERFACES-3621, All Flash operations cause NPE with distributable webapp and no session > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2779) Create a jUnit result panel to show test results

by Juraj Soltes (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2779?page=com.atlassian.jira.plugi... ] Juraj Soltes updated DROOLS-2779: --------------------------------- Tester: Juraj Soltes (was: Klara Kufova) > Create a jUnit result panel to show test results > ------------------------------------------------ > > Key: DROOLS-2779 > URL: https://issues.jboss.org/browse/DROOLS-2779 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Toni Rikkola > Labels: ScenarioSimulation > > Reuse test scenario result component to show jUnit results. > Convert result layout to new HTML/CSS -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2780) Create a right panel for expression builder/cheatsheet

by Juraj Soltes (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2780?page=com.atlassian.jira.plugi... ] Juraj Soltes updated DROOLS-2780: --------------------------------- Tester: Juraj Soltes (was: Klara Kufova) > Create a right panel for expression builder/cheatsheet > ------------------------------------------------------ > > Key: DROOLS-2780 > URL: https://issues.jboss.org/browse/DROOLS-2780 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Labels: ScenarioSimulation > > Create a panel on the right with a tab selector and two tabs: expression builder and cheatsheet. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2689) The ability to hide an asset based on a flag

by Juraj Soltes (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2689?page=com.atlassian.jira.plugi... ] Juraj Soltes updated DROOLS-2689: --------------------------------- Tester: Juraj Soltes (was: Klara Kufova) > The ability to hide an asset based on a flag > -------------------------------------------- > > Key: DROOLS-2689 > URL: https://issues.jboss.org/browse/DROOLS-2689 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Juraj Soltes > Assignee: Toni Rikkola > Labels: ScenarioSimulation > > Experimental feature (disabled by default). > If the user wants to enable the Add new Simulation Scenario option she can use a command line parameter to enable it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2018