April 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-148) Create Sikuli server environment on selenium server

by Jeeva Kandasamy (JIRA)

[ https://issues.jboss.org/browse/SWSQE-148?page=com.atlassian.jira.plugin.... ] Jeeva Kandasamy resolved SWSQE-148. ----------------------------------- Resolution: Done https://github.com/jkandasa/sekuli > Create Sikuli server environment on selenium server > --------------------------------------------------- > > Key: SWSQE-148 > URL: https://issues.jboss.org/browse/SWSQE-148 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Jeeva Kandasamy > Assignee: Jeeva Kandasamy > > For this task, we have to add Sikuli supported libraries on selenium docker -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-147) Add selenium-sikuli support for Python

by Jeeva Kandasamy (JIRA)

[ https://issues.jboss.org/browse/SWSQE-147?page=com.atlassian.jira.plugin.... ] Jeeva Kandasamy resolved SWSQE-147. ----------------------------------- Resolution: Done https://github.com/jkandasa/sekuli > Add selenium-sikuli support for Python > -------------------------------------- > > Key: SWSQE-147 > URL: https://issues.jboss.org/browse/SWSQE-147 > Project: Kiali QE > Issue Type: QE Task > Reporter: Jeeva Kandasamy > Assignee: Jeeva Kandasamy > > Currently, we do not have any option(AFAIK) any option to run Sikuli on a remote machine. But we have Java option. We have to implement REST API support on Java side(selenium side) to run Sikuli. When we call via REST we can add any type of client. > Here we have three type of work, > 1. Create Sikuli environment on the remote machine > 2. Add REST API for Sikuli on the server side(Java implementation) > 3. Add REST Client to communicate with Sikuli service on remote machine -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-169) Restructure Python automation framework - it is fetching data very slowly

by Jeeva Kandasamy (JIRA)

[ https://issues.jboss.org/browse/SWSQE-169?page=com.atlassian.jira.plugin.... ] Jeeva Kandasamy reassigned SWSQE-169: ------------------------------------- Assignee: Jeeva Kandasamy (was: Michael Foley) > Restructure Python automation framework - it is fetching data very slowly > ------------------------------------------------------------------------- > > Key: SWSQE-169 > URL: https://issues.jboss.org/browse/SWSQE-169 > Project: Kiali QE > Issue Type: QE Task > Reporter: Jeeva Kandasamy > Assignee: Jeeva Kandasamy > > https://github.com/Kiali-QE/kiali-qe-python fetching data from slowly and needs some improvements in the overall structure. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-191) Add Sekuli into Zalenium

by Jeeva Kandasamy (JIRA)

Jeeva Kandasamy created SWSQE-191: ------------------------------------- Summary: Add Sekuli into Zalenium Key: SWSQE-191 URL: https://issues.jboss.org/browse/SWSQE-191 Project: Kiali QE Issue Type: QE Task Reporter: Jeeva Kandasamy Assignee: Michael Foley https://github.com/jkandasa/sekuli -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-150) Python remote Sikuli client

by Jeeva Kandasamy (JIRA)

[ https://issues.jboss.org/browse/SWSQE-150?page=com.atlassian.jira.plugin.... ] Jeeva Kandasamy resolved SWSQE-150. ----------------------------------- Resolution: Done https://github.com/jkandasa/sekuli/tree/master/sekuli_python > Python remote Sikuli client > --------------------------- > > Key: SWSQE-150 > URL: https://issues.jboss.org/browse/SWSQE-150 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Jeeva Kandasamy > Assignee: Jeeva Kandasamy > > Create Python client library to run Sikuli actions from remote via Selenium grid/node -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-149) Add Java REST API server code for selenium-Sikuli environment

by Jeeva Kandasamy (JIRA)

[ https://issues.jboss.org/browse/SWSQE-149?page=com.atlassian.jira.plugin.... ] Jeeva Kandasamy resolved SWSQE-149. ----------------------------------- Resolution: Done https://github.com/jkandasa/sekuli > Add Java REST API server code for selenium-Sikuli environment > ------------------------------------------------------------- > > Key: SWSQE-149 > URL: https://issues.jboss.org/browse/SWSQE-149 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Jeeva Kandasamy > Assignee: Jeeva Kandasamy > > In this task, have to add the following code, > * Sikuli node code for selenium node > * Selenium grid code for Sikuli > * REST API to trigger sikuli actions on remote -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-190) Add a filter to remove some jobs - Push Jenkins console log

by Jeeva Kandasamy (JIRA)

[ https://issues.jboss.org/browse/SWSQE-190?page=com.atlassian.jira.plugin.... ] Jeeva Kandasamy updated SWSQE-190: ---------------------------------- Summary: Add a filter to remove some jobs - Push Jenkins console log (was: Add a filter to remove some jobs) > Add a filter to remove some jobs - Push Jenkins console log > ----------------------------------------------------------- > > Key: SWSQE-190 > URL: https://issues.jboss.org/browse/SWSQE-190 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Jeeva Kandasamy > Assignee: Jeeva Kandasamy > > For now, there is no filter to skip posting some of the jobs. We need to add some of type filter to skip posting some jobs status on PR comment. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-190) Add a filter to remove some jobs

by Jeeva Kandasamy (JIRA)

Jeeva Kandasamy created SWSQE-190: ------------------------------------- Summary: Add a filter to remove some jobs Key: SWSQE-190 URL: https://issues.jboss.org/browse/SWSQE-190 Project: Kiali QE Issue Type: Sub-task Reporter: Jeeva Kandasamy Assignee: Jeeva Kandasamy For now, there is no filter to skip posting some of the jobs. We need to add some of type filter to skip posting some jobs status on PR comment. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10094) [Artemis 2.x upgrade] libAIO does not get loaded on RHEL 6 x86_64

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-10094?page=com.atlassian.jira.plugin... ] Miroslav Novak edited comment on WFLY-10094 at 4/26/18 8:51 AM: ---------------------------------------------------------------- The cause is that GLIBC_2.14 is missing: {code}java.lang.UnsatisfiedLinkError: /tmp/jboss-eap/modules/system/layers/base/org/apache/activemq/artemis/journal/main/lib/linux-x86_64/libartemis-native-64.so: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /tmp/jboss-eap/modules/system/layers/base/org/apache/activemq/artemis/journal/main/lib/linux-x86_64/libartemis-native-64.so){code} However GLIBC is present on RHEL 6 but in older version 2.12. I've read something around this and problem is that libartemis-native-64.so was compiled on RHEL 7 where is newer GLIBC_2.14 version. So libartemis-native-64.so should be compiled on RHEL6 to fix this. Just from curiosity when I tried to compile glibc-2.14 and added it to LD_LIBRARY_PATH AIO got loaded on RHEL 6. was (Author: mnovak): The cause is that GLIBC_2.14 is missing: {code}java.lang.UnsatisfiedLinkError: /tmp/jboss-eap/modules/system/layers/base/org/apache/activemq/artemis/journal/main/lib/linux-x86_64/libartemis-native-64.so: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /tmp/jboss-eap/modules/system/layers/base/org/apache/activemq/artemis/journal/main/lib/linux-x86_64/libartemis-native-64.so){code} However GLIBC is present on RHEL 6 but in older version 2.12. I've read something around this and problem is that libartemis-native-64.so was compiled on RHEL 7 where is newer GLIBC_2.14 version. So libartemis-native-64.so should be compiled on RHEL6 to fix this. Just from curiosity when I tried to compile glibc-2.14 and added it to LD_LIBRARY_PATH and AIO got loaded on RHEL 6. > [Artemis 2.x upgrade] libAIO does not get loaded on RHEL 6 x86_64 > ----------------------------------------------------------------- > > Key: WFLY-10094 > URL: https://issues.jboss.org/browse/WFLY-10094 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Priority: Blocker > Labels: activemq, feature-branch-blocker > > LibAIO does not get loaded on RHEL 6 x86_64: > {code} > [hudson@rhel6-large-2723 bin]$ sh standalone.sh -c standalone-full-ha.xml -Djboss.socket.binding.port-offset=1000 > ========================================================================= > JBoss Bootstrap Environment > JBOSS_HOME: /tmp/jboss-eap > JAVA: java > JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true > ========================================================================= > ... > 10:14:31,918 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0075: AIO wasn't located on this platform, it will fall back to using pure Java NIO. Your platform is Linux, install LibAIO to enable the AIO journal and achieve optimal performance. > 10:14:32,017 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=true,journalDirectory=/tmp/jboss-eap/standalone/data/activemq/journal,bindingsDirectory=/tmp/jboss-eap/standalone/data/activemq/bindings,largeMessagesDirectory=/tmp/jboss-eap/standalone/data/activemq/largemessages,pagingDirectory=/tmp/jboss-eap/standalone/data/activemq/paging) > 10:14:32,110 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221013: Using NIO Journal > ... > {code} > libAIO in artemis journal module from WF branch. Not from Artemis 2.5.0.Final tag. > Wildfly: https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (06c878a313d3cad323889d017e60fd5533204d1a) > Artemis: upstreadm master (577b62d5210cdcc0f86ab9bb1b24e944c877dfe7) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10094) [Artemis 2.x upgrade] libAIO does not get loaded on RHEL 6 x86_64

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-10094?page=com.atlassian.jira.plugin... ] Miroslav Novak commented on WFLY-10094: --------------------------------------- The cause is that GLIBC_2.14 is missing: {code}java.lang.UnsatisfiedLinkError: /tmp/jboss-eap/modules/system/layers/base/org/apache/activemq/artemis/journal/main/lib/linux-x86_64/libartemis-native-64.so: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /tmp/jboss-eap/modules/system/layers/base/org/apache/activemq/artemis/journal/main/lib/linux-x86_64/libartemis-native-64.so){code} However GLIBC is present on RHEL 6 but in older version 2.12. I've read something around this and problem is that libartemis-native-64.so was compiled on RHEL 7 where is newer GLIBC_2.14 version. So libartemis-native-64.so should be compiled on RHEL6 to fix this. Just from curiosity when I tried to compile glibc-2.14 and added it to LD_LIBRARY_PATH and AIO got loaded on RHEL 6. > [Artemis 2.x upgrade] libAIO does not get loaded on RHEL 6 x86_64 > ----------------------------------------------------------------- > > Key: WFLY-10094 > URL: https://issues.jboss.org/browse/WFLY-10094 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Priority: Blocker > Labels: activemq, feature-branch-blocker > > LibAIO does not get loaded on RHEL 6 x86_64: > {code} > [hudson@rhel6-large-2723 bin]$ sh standalone.sh -c standalone-full-ha.xml -Djboss.socket.binding.port-offset=1000 > ========================================================================= > JBoss Bootstrap Environment > JBOSS_HOME: /tmp/jboss-eap > JAVA: java > JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true > ========================================================================= > ... > 10:14:31,918 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0075: AIO wasn't located on this platform, it will fall back to using pure Java NIO. Your platform is Linux, install LibAIO to enable the AIO journal and achieve optimal performance. > 10:14:32,017 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=true,journalDirectory=/tmp/jboss-eap/standalone/data/activemq/journal,bindingsDirectory=/tmp/jboss-eap/standalone/data/activemq/bindings,largeMessagesDirectory=/tmp/jboss-eap/standalone/data/activemq/largemessages,pagingDirectory=/tmp/jboss-eap/standalone/data/activemq/paging) > 10:14:32,110 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221013: Using NIO Journal > ... > {code} > libAIO in artemis journal module from WF branch. Not from Artemis 2.5.0.Final tag. > Wildfly: https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (06c878a313d3cad323889d017e60fd5533204d1a) > Artemis: upstreadm master (577b62d5210cdcc0f86ab9bb1b24e944c877dfe7) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2018