August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-789) UI Automations - Add more checks of Gateway and Load Balancer in Routing Wizard.

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-789?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan resolved SWSQE-789. ---------------------------------- Resolution: Done > UI Automations - Add more checks of Gateway and Load Balancer in Routing Wizard. > -------------------------------------------------------------------------------- > > Key: SWSQE-789 > URL: https://issues.jboss.org/browse/SWSQE-789 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > Routing CRUD tests fails randomly when checking Actions menu items enable/disable states. > Probably we need to add waits after each action which will cause menu items state change and checking is done very fast. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-789) UI Automations - Add more checks of Gateway and Load Balancer in Routing Wizard.

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-789?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan commented on SWSQE-789: -------------------------------------- https://github.com/Kiali-QE/kiali-qe-python/pull/186 > UI Automations - Add more checks of Gateway and Load Balancer in Routing Wizard. > -------------------------------------------------------------------------------- > > Key: SWSQE-789 > URL: https://issues.jboss.org/browse/SWSQE-789 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > Routing CRUD tests fails randomly when checking Actions menu items enable/disable states. > Probably we need to add waits after each action which will cause menu items state change and checking is done very fast. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4590) Upgrade jboss-logmanager from 2.1.13.Final to 2.1.14.Final

by James Perkins (Jira)

James Perkins created WFCORE-4590: ------------------------------------- Summary: Upgrade jboss-logmanager from 2.1.13.Final to 2.1.14.Final Key: WFCORE-4590 URL: https://issues.jboss.org/browse/WFCORE-4590 Project: WildFly Core Issue Type: Component Upgrade Components: Logging Reporter: James Perkins Assignee: James Perkins Upgrade jboss-logmanager from 2.1.13.Final to 2.1.14.Final. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4579) Upgrade jboss-logging from 3.4.0.Final to 3.4.1.Final

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4579?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-4579: ---------------------------------- Summary: Upgrade jboss-logging from 3.4.0.Final to 3.4.1.Final (was: Upgrade jboss-logging from 2.4.0.Final to 2.4.1.Final) > Upgrade jboss-logging from 3.4.0.Final to 3.4.1.Final > ----------------------------------------------------- > > Key: WFCORE-4579 > URL: https://issues.jboss.org/browse/WFCORE-4579 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Affects Versions: 10.0.0.Beta2 > Reporter: Chao Wang > Assignee: James Perkins > Priority: Major > Labels: downstream_dependency > > Upgrade org.jboss.logging:jboss-logging from 2.4.0.Final to 2.4.1.Final. > https://github.com/jboss-logging/jboss-logging/compare/2.4.0.Final...2.4.... -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4579) Upgrade jboss-logging from 3.4.0.Final to 3.4.1.Final

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4579?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-4579: ---------------------------------- Description: Upgrade org.jboss.logging:jboss-logging from 3.4.0.Final to 3.4.1.Final. https://github.com/jboss-logging/jboss-logging/compare/3.4.0.Final...3.4.... was: Upgrade org.jboss.logging:jboss-logging from 2.4.0.Final to 2.4.1.Final. https://github.com/jboss-logging/jboss-logging/compare/2.4.0.Final...2.4.... > Upgrade jboss-logging from 3.4.0.Final to 3.4.1.Final > ----------------------------------------------------- > > Key: WFCORE-4579 > URL: https://issues.jboss.org/browse/WFCORE-4579 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Affects Versions: 10.0.0.Beta2 > Reporter: Chao Wang > Assignee: James Perkins > Priority: Major > Labels: downstream_dependency > > Upgrade org.jboss.logging:jboss-logging from 3.4.0.Final to 3.4.1.Final. > https://github.com/jboss-logging/jboss-logging/compare/3.4.0.Final...3.4.... -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4579) Upgrade jboss-logging from 2.4.0.Final to 2.4.1.Final

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4579?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-4579: ---------------------------------- Description: Upgrade org.jboss.logging:jboss-logging from 2.4.0.Final to 2.4.1.Final. https://github.com/jboss-logging/jboss-logging/compare/2.4.0.Final...2.4.... was: Upgrade org.jboss.logging:jboss-logging from 3.4.0.Final to 3.4.1.Final. https://github.com/jboss-logging/jboss-logging/compare/3.4.0.Final...3.4.... > Upgrade jboss-logging from 2.4.0.Final to 2.4.1.Final > ----------------------------------------------------- > > Key: WFCORE-4579 > URL: https://issues.jboss.org/browse/WFCORE-4579 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Affects Versions: 10.0.0.Beta2 > Reporter: Chao Wang > Assignee: James Perkins > Priority: Major > Labels: downstream_dependency > > Upgrade org.jboss.logging:jboss-logging from 2.4.0.Final to 2.4.1.Final. > https://github.com/jboss-logging/jboss-logging/compare/2.4.0.Final...2.4.... -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4579) Upgrade jboss-logging from 2.4.0.Final to 2.4.1.Final

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4579?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-4579: ---------------------------------- Summary: Upgrade jboss-logging from 2.4.0.Final to 2.4.1.Final (was: Upgrade jboss-logging from 3.4.0.Final to 3.4.1.Final) > Upgrade jboss-logging from 2.4.0.Final to 2.4.1.Final > ----------------------------------------------------- > > Key: WFCORE-4579 > URL: https://issues.jboss.org/browse/WFCORE-4579 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Affects Versions: 10.0.0.Beta2 > Reporter: Chao Wang > Assignee: James Perkins > Priority: Major > Labels: downstream_dependency > > Upgrade org.jboss.logging:jboss-logging from 3.4.0.Final to 3.4.1.Final. > https://github.com/jboss-logging/jboss-logging/compare/3.4.0.Final...3.4.... -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-259) Named filters throw an IllegalArgumentException if they are embedded in an expression

by James Perkins (Jira)

[ https://issues.jboss.org/browse/LOGMGR-259?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-259: --------------------------------- Fix Version/s: 1.3.3.Final 1.4.4.Final 1.5.10.Final 2.0.12.Final 2.1.14.Final 2.2.0.Final > Named filters throw an IllegalArgumentException if they are embedded in an expression > ------------------------------------------------------------------------------------- > > Key: LOGMGR-259 > URL: https://issues.jboss.org/browse/LOGMGR-259 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > Fix For: 1.3.3.Final, 1.4.4.Final, 1.5.10.Final, 2.0.12.Final, 2.1.14.Final, 2.2.0.Final > > > A named filter, one that was added via the configuration API, will throw an {{IllegalArgumentException}} if they are embedded in a filter expression. > The following should be a valid expression as "all" is a changed filter and "test" is the manually created filter. > {code} > logContextConfiguration.addFilterConfiguration(null, "org.jboss.filter.Test", "test"); > logContextConfiguration.getLoggerConfiguration("").setFilter("all(test)"); > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-259) Named filters throw an IllegalArgumentException if they are embedded in an expression

by James Perkins (Jira)

[ https://issues.jboss.org/browse/LOGMGR-259?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-259: --------------------------------- Git Pull Request: https://github.com/jboss-logging/jboss-logmanager/pull/272, https://github.com/jboss-logging/jboss-logmanager/pull/273, https://github.com/jboss-logging/jboss-logmanager/pull/274, https://github.com/jboss-logging/jboss-logmanager/pull/275, https://github.com/jboss-logging/jboss-logmanager/pull/276 > Named filters throw an IllegalArgumentException if they are embedded in an expression > ------------------------------------------------------------------------------------- > > Key: LOGMGR-259 > URL: https://issues.jboss.org/browse/LOGMGR-259 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > > A named filter, one that was added via the configuration API, will throw an {{IllegalArgumentException}} if they are embedded in a filter expression. > The following should be a valid expression as "all" is a changed filter and "test" is the manually created filter. > {code} > logContextConfiguration.addFilterConfiguration(null, "org.jboss.filter.Test", "test"); > logContextConfiguration.getLoggerConfiguration("").setFilter("all(test)"); > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-259) Named filters throw an IllegalArgumentException if they are embedded in an expression

by James Perkins (Jira)

James Perkins created LOGMGR-259: ------------------------------------ Summary: Named filters throw an IllegalArgumentException if they are embedded in an expression Key: LOGMGR-259 URL: https://issues.jboss.org/browse/LOGMGR-259 Project: JBoss Log Manager Issue Type: Bug Reporter: James Perkins Assignee: James Perkins A named filter, one that was added via the configuration API, will throw an {{IllegalArgumentException}} if they are embedded in a filter expression. The following should be a valid expression as "all" is a changed filter and "test" is the manually created filter. {code} logContextConfiguration.addFilterConfiguration(null, "org.jboss.filter.Test", "test"); logContextConfiguration.getLoggerConfiguration("").setFilter("all(test)"); {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 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 August 2019