March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4385) DomainTestSupport and DomainLifecycleUtil should be AutoCloseable

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-4385: ---------------------------------------- Summary: DomainTestSupport and DomainLifecycleUtil should be AutoCloseable Key: WFCORE-4385 URL: https://issues.jboss.org/browse/WFCORE-4385 Project: WildFly Core Issue Type: Enhancement Components: Management, Test Suite Reporter: Brian Stansberry Assignee: Brian Stansberry Let DomainTestSupport and DomainLifecycleUtil be used in try-with-resources. Once closed the objects should not be usable; i.e. this differs from stop(), where start() can be called again. DomainTestSupport.stop() can closes the DomainLifecycleUtil objects it controls though, preventing their subsequent use. This will protect against the WFCORE-4384 problem. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4384) Clean up CachedDcDomainTestCase handling of domain lifecycle

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-4384: ---------------------------------------- Summary: Clean up CachedDcDomainTestCase handling of domain lifecycle Key: WFCORE-4384 URL: https://issues.jboss.org/browse/WFCORE-4384 Project: WildFly Core Issue Type: Task Components: Management, Test Suite Reporter: Brian Stansberry Assignee: Brian Stansberry CachedDcDomainTestCase has the same problem that led to the odd lifecycle handling in ReadOnlyModeTestCase that will be corrected in WFCORE-4381. It uses DomainTestSupport.stop() as a shorthand for stopping the HCs, rather than using the DomainLifecycleUtil for those HCs to stop them. The problem is DomainTestSupport.stop() also closes down the Endpoint that is used by those DomainLifecycleUtil instances. The instances remain though and are still used. The problem is once the Endpoint is stopped, those DomainLifecycleUtil instances can no longer connect to the HCs. So all the util code in DomainLifecycleUtil for executing ops or managing HC lifecycle no longer works. The result is CachedDcDomainTestCase has all sorts of custom lifecycle code that's a possible source of bugs. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4383) DomainCommandBuilder ignores the specified PC/HC JVM

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-4383: ---------------------------------------- Summary: DomainCommandBuilder ignores the specified PC/HC JVM Key: WFCORE-4383 URL: https://issues.jboss.org/browse/WFCORE-4383 Project: WildFly Core Issue Type: Bug Components: Management, Test Suite Affects Versions: 9.0.0.Beta1 Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 9.0.0.Beta2 The WFCORE-4329 fix results in DomainCommandBuilder ignoring a configured JVM and instead using Jvm.current() for the HC and PC. https://github.com/wildfly/wildfly-core/pull/3692/files#diff-86e68a2cbfc6... This is the cause of mixed-domain testsuite failures in full when the test driver uses JDK 11. The test's configuring of the PC/HC to use JDK 8 is being ignored. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11896) Allow mixed domain tests to be ignored if no VM the legacy host can use is available

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11896?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-11896: ------------------------------------ Description: The mixed domain tests won't work properly if the VM running the testsuite is not usable by the legacy host controllers. If the test run is configured with property java8.home set to the root of a JDK 8 installation, then the legacy hosts will be started with JDK 8, which may work. But this has flaws: * Test jobs may not have java8.home configured, but this suite should still do something reasonable. * Some legacy host versions it might be better to test with something other than 8, e.g. 11. * In the future some legacy host versions might not support 8, so we want a more complex mechanism. To address the first point, the Version.AsVersion enum should include the min and max JVM versions acceptable for that host version. The testsuite in mixed-domain should be ignored if there is a mismatch and the following isn't configured: The testsuite should check property jboss.test.legacy.host.javaX.home and if set configure the legacy slave to use the VM indicated by the value. The 'X' in 'javaX' is a value between the min and the max value the legacy host version supports. All should be tried until a match is found. was: The mixed domain tests won't work properly if the VM running the testsuite is not usable by the legacy host controllers. If the test run is configured wit property java8.home set to the root of a JDK 8 installation, then the legacy hosts will be started with JDK 8, which may work. But this has flaws: * Test jobs may not have java8.home configured, but this suite should still do something reasonable. * Some legacy host versions it might be better to test with something other than 8, e.g. 11 * In the future some legacy host versions might not support 8, so we want a more complex mechanism. To address the first point, the Version.AsVersion enum should include the min and max JVM versions acceptable for that host version. The testsuite in mixed-domain should be ignored if there is a mismatch and the following isn't configured: The testsuite should check property jboss.test.legacy.host.javaX.home and if set configure the legacy slave to use the VM indicated by the value. The 'X' in 'javaX' is a value between the min and the max value the legacy host version supports. All should be tried until a match is found. > Allow mixed domain tests to be ignored if no VM the legacy host can use is available > ------------------------------------------------------------------------------------ > > Key: WFLY-11896 > URL: https://issues.jboss.org/browse/WFLY-11896 > Project: WildFly > Issue Type: Enhancement > Components: Management, Test Suite > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > > The mixed domain tests won't work properly if the VM running the testsuite is not usable by the legacy host controllers. If the test run is configured with property java8.home set to the root of a JDK 8 installation, then the legacy hosts will be started with JDK 8, which may work. But this has flaws: > * Test jobs may not have java8.home configured, but this suite should still do something reasonable. > * Some legacy host versions it might be better to test with something other than 8, e.g. 11. > * In the future some legacy host versions might not support 8, so we want a more complex mechanism. > To address the first point, the Version.AsVersion enum should include the min and max JVM versions acceptable for that host version. The testsuite in mixed-domain should be ignored if there is a mismatch and the following isn't configured: > The testsuite should check property jboss.test.legacy.host.javaX.home and if set configure the legacy slave to use the VM indicated by the value. The 'X' in 'javaX' is a value between the min and the max value the legacy host version supports. All should be tried until a match is found. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11896) Allow mixed domain tests to be ignored if no VM the legacy host can use is available

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-11896: --------------------------------------- Summary: Allow mixed domain tests to be ignored if no VM the legacy host can use is available Key: WFLY-11896 URL: https://issues.jboss.org/browse/WFLY-11896 Project: WildFly Issue Type: Enhancement Components: Management, Test Suite Reporter: Brian Stansberry Assignee: Brian Stansberry The mixed domain tests won't work properly if the VM running the testsuite is not usable by the legacy host controllers. If the test run is configured wit property java8.home set to the root of a JDK 8 installation, then the legacy hosts will be started with JDK 8, which may work. But this has flaws: * Test jobs may not have java8.home configured, but this suite should still do something reasonable. * Some legacy host versions it might be better to test with something other than 8, e.g. 11 * In the future some legacy host versions might not support 8, so we want a more complex mechanism. To address the first point, the Version.AsVersion enum should include the min and max JVM versions acceptable for that host version. The testsuite in mixed-domain should be ignored if there is a mismatch and the following isn't configured: The testsuite should check property jboss.test.legacy.host.javaX.home and if set configure the legacy slave to use the VM indicated by the value. The 'X' in 'javaX' is a value between the min and the max value the legacy host version supports. All should be tried until a match is found. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-109) Update syslog handler attributes

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-109?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-109: --------------------------------- Issue Type: Feature Request (was: Enhancement) > Update syslog handler attributes > -------------------------------- > > Key: WFCORE-109 > URL: https://issues.jboss.org/browse/WFCORE-109 > Project: WildFly Core > Issue Type: Feature Request > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > > The syslog handler does not currently expose the formatter for formatting messages. There will also be changes in a future logmanager release for TCP support and various other properties based on the new TCP support. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4382) Upgrade Byteman from 4.0.5 to 4.0.6

by Richard Opalka (Jira)

[ https://issues.jboss.org/browse/WFCORE-4382?page=com.atlassian.jira.plugi... ] Richard Opalka updated WFCORE-4382: ----------------------------------- Labels: jdk13 (was: ) > Upgrade Byteman from 4.0.5 to 4.0.6 > ----------------------------------- > > Key: WFCORE-4382 > URL: https://issues.jboss.org/browse/WFCORE-4382 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Test Suite > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Major > Labels: jdk13 > Fix For: 9.0.0.Beta2 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4382) Upgrade Byteman from 4.0.5 to 4.0.6

by Richard Opalka (Jira)

Richard Opalka created WFCORE-4382: -------------------------------------- Summary: Upgrade Byteman from 4.0.5 to 4.0.6 Key: WFCORE-4382 URL: https://issues.jboss.org/browse/WFCORE-4382 Project: WildFly Core Issue Type: Component Upgrade Components: Test Suite Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 9.0.0.Beta2 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-232) Load Test on Kiali API

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-232?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-232. ------------------------------------------- Resolution: Done Handled on KIALI-1924 > Load Test on Kiali API > ---------------------- > > Key: SWSQE-232 > URL: https://issues.jboss.org/browse/SWSQE-232 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > - Test Kiali Rest API with multiple/concurrent users > [~mmahoney] suggested to run the load generation from a different OS cluster then that of the Kiali under test, thus avoiding perormance impact by load generation itself. > [~pavol_loffay] suggested to configure k8s resources and quotas -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-272) Set Up Kubernetes Cluster

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-272?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo closed SWSQE-272. ----------------------------------------- Resolution: Out of Date > Set Up Kubernetes Cluster > ------------------------- > > Key: SWSQE-272 > URL: https://issues.jboss.org/browse/SWSQE-272 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Matt Mahoney > Assignee: Guilherme Baufaker Rêgo > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

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 March 2019