May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-113) Allocate OpenShift and Jenkins resources for testing Jaeger productized images

by Kevin Earls (JIRA)

[ https://issues.jboss.org/browse/SWSQE-113?page=com.atlassian.jira.plugin.... ] Kevin Earls reopened SWSQE-113: ------------------------------- Sorry if there has been a misunderstanding here, but I still do not have the resources I need for this. [~hhovsepy] suggested I create a job on Jenkins2 and use B15 to access the Jaeger instance that is installed with Istio. However, my initial attempts to do this have failed. I sent the following details out in email earlier today: -- If I run on jenkins2 and use "agent { label 'mvn' }", what cluster does it actually run on? (Please let me know if there is an oc command that will tell me this.) . I'm trying to run the same code I was running on B15 as part of this job http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/kearls-test/ but the tests are failing. -- When I run the job it says I'm using the "jenkins-slaves" project, but I don't see that on B15 or B12. For test development and debugging I will need a project that is not torn down at the end of the job. Is this possible. So I either need a project on B15 which is not torn down when the node is restarted, or an agent on Jenkins2 that runs on B15 and does not remove the project when it finishes. > Allocate OpenShift and Jenkins resources for testing Jaeger productized images > ------------------------------------------------------------------------------ > > Key: SWSQE-113 > URL: https://issues.jboss.org/browse/SWSQE-113 > Project: Kiali QE > Issue Type: QE Task > Reporter: Kevin Earls > Assignee: Guilherme Baufaker Rêgo > > I need internal Jenkins and OpenShift resources for https://issues.jboss.org/browse/KIALI-336 which covers testing productized Jaeger images. I have already started working with [~fbrychta] but we have not completely resolved this yet. > I can work with either of these two options > -- A project on an OpenShift Cluster where I can create my own Jenkins instance. > -- An external Jenkins which has an agent defined which can run on OpenShift. > I'm not completely sure if the second solution will work, as when I run tests I will need to have access to ports that are not externally accessible. In that case I'd be happy to use the first solution. > Finally, this will just be for smoke and possibly simple functional tests, so I won't need high levels of resources. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3797) Logging Subsystem test failures on IBM jdk

by Petr Kremensky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3797?page=com.atlassian.jira.plugi... ] Petr Kremensky updated WFCORE-3797: ----------------------------------- Steps to Reproduce: {noformat}# switch to IBM jdk mvn test -pl logging{noformat} was: # switch to IBM jdk mvn test -pl logging > Logging Subsystem test failures on IBM jdk > ------------------------------------------ > > Key: WFCORE-3797 > URL: https://issues.jboss.org/browse/WFCORE-3797 > Project: WildFly Core > Issue Type: Bug > Components: Logging, Test Suite > Affects Versions: 5.0.0.Alpha1, 5.0.0.Alpha2, 5.0.0.Alpha3, 5.0.0.Alpha4 > Environment: {noformat} > Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00) > Maven home: /usr/lib/maven > Java version: 1.8.0_161, vendor: IBM Corporation > Java home: /usr/lib/java/ibm-java-8.0-5.11/jre > {noformat} > Reporter: Petr Kremensky > Assignee: James Perkins > > WildFly: Logging Subsystem unit tests fails on IBM jdk with: > {noformat} > java.lang.IllegalStateException: WFLYLOG0078: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager" > at org.jboss.as.logging.LoggingExtension.initialize(LoggingExtension.java:168) > at org.jboss.as.subsystem.test.TestModelControllerService.preBoot(TestModelControllerService.java:158) > at org.jboss.as.model.test.ModelTestModelControllerService.boot(ModelTestModelControllerService.java:264) > at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:419) > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:372) > at java.lang.Thread.run(Thread.java:811) > {noformat} > The test works fine with *4.0.0.Final*, starts failing in *5.0.0.Alpha1*. > This doens't look like a functional issue to me as I was able to workaround the issue by either running the test with the older surefire instance ( -Dversion.surefire.plugin=2.19 is the last working ) or by extending {{surefire.system.args}} in pom.xml with {{-Djava.util.logging.manager=org.jboss.logmanager.LogManager}}. The other however produces the following warnings upon test execution > {noformat} > ... > [WARNING] The system property java.util.logging.manager is configured twice! The property appears in <argLine/> and any of <systemPropertyVariables/>, <systemProperties/> or user property. > [INFO] > [INFO] ------------------------------------------------------- > [INFO] T E S T S > [INFO] ------------------------------------------------------- > [INFO] Running org.jboss.as.logging.HandlerLegacyOperationsTestCase > [WARNING] Corrupted STDOUT by directly writing to native stream in forked JVM 1. See FAQ web page and the dump file /home/pkremens/devel/wildfly-core/logging/target/surefire-reports/2018-05-03T13-49-32_779-jvmRun1.dumpstream > ... > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3797) Logging Subsystem test failures on IBM jdk

by Petr Kremensky (JIRA)

Petr Kremensky created WFCORE-3797: -------------------------------------- Summary: Logging Subsystem test failures on IBM jdk Key: WFCORE-3797 URL: https://issues.jboss.org/browse/WFCORE-3797 Project: WildFly Core Issue Type: Bug Components: Logging, Test Suite Affects Versions: 5.0.0.Alpha4, 5.0.0.Alpha3, 5.0.0.Alpha2, 5.0.0.Alpha1 Environment: {noformat} Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00) Maven home: /usr/lib/maven Java version: 1.8.0_161, vendor: IBM Corporation Java home: /usr/lib/java/ibm-java-8.0-5.11/jre {noformat} Reporter: Petr Kremensky Assignee: James Perkins WildFly: Logging Subsystem unit tests fails on IBM jdk with: {noformat} java.lang.IllegalStateException: WFLYLOG0078: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager" at org.jboss.as.logging.LoggingExtension.initialize(LoggingExtension.java:168) at org.jboss.as.subsystem.test.TestModelControllerService.preBoot(TestModelControllerService.java:158) at org.jboss.as.model.test.ModelTestModelControllerService.boot(ModelTestModelControllerService.java:264) at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:419) at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:372) at java.lang.Thread.run(Thread.java:811) {noformat} The test works fine with *4.0.0.Final*, starts failing in *5.0.0.Alpha1*. This doens't look like a functional issue to me as I was able to workaround the issue by either running the test with the older surefire instance ( -Dversion.surefire.plugin=2.19 is the last working ) or by extending {{surefire.system.args}} in pom.xml with {{-Djava.util.logging.manager=org.jboss.logmanager.LogManager}}. The other however produces the following warnings upon test execution {noformat} ... [WARNING] The system property java.util.logging.manager is configured twice! The property appears in <argLine/> and any of <systemPropertyVariables/>, <systemProperties/> or user property. [INFO] [INFO] ------------------------------------------------------- [INFO] T E S T S [INFO] ------------------------------------------------------- [INFO] Running org.jboss.as.logging.HandlerLegacyOperationsTestCase [WARNING] Corrupted STDOUT by directly writing to native stream in forked JVM 1. See FAQ web page and the dump file /home/pkremens/devel/wildfly-core/logging/target/surefire-reports/2018-05-03T13-49-32_779-jvmRun1.dumpstream ... {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-9) Elytron permission-set should throw exception for non-existent permission

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFWIP-9?page=com.atlassian.jira.plugin.sy... ] Kabir Khan updated WFWIP-9: --------------------------- Component/s: Security > Elytron permission-set should throw exception for non-existent permission > ------------------------------------------------------------------------- > > Key: WFWIP-9 > URL: https://issues.jboss.org/browse/WFWIP-9 > Project: WildFly WIP > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Farah Juma > Labels: WFCORE-3596 > > When non-existent permission (e.g. when there is a typo in class-name) is added to Elytron permission-set then exception should be thrown. It should throw exception for wrong class-name as well as wrong module. > See issue WFCORE-3796 for more details. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10318) Use Galleon to build Wild full distributions

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFLY-10318?page=com.atlassian.jira.plugin... ] Alexey Loubyansky updated WFLY-10318: ------------------------------------- Description: Switch from the current feature-pack-based provisioning to Galleon and WildFly Galleon plugins. Create galleon feature packs as Maven artifacts and use them to produce the thin and fat servlet, full and other testsuite distributions. The legacy servlet and full feature-packs should still be built. They could still be used to produce the legacy builds and distributions by activating Maven profiles. was: Switch from the current build tools to the Galleon and WildFly Galleon plugins. Create galleon feature packs as Maven artifacts and use them to produce the thin and fat servlet, full and other testsuite distributions. The legacy servlet and full feature-packs should still be built. They could still be used to produce the legacy builds and distributions by activating Maven profiles. > Use Galleon to build Wild full distributions > -------------------------------------------- > > Key: WFLY-10318 > URL: https://issues.jboss.org/browse/WFLY-10318 > Project: WildFly > Issue Type: Task > Components: Server > Reporter: Alexey Loubyansky > Assignee: Jason Greene > > Switch from the current feature-pack-based provisioning to Galleon and WildFly Galleon plugins. > Create galleon feature packs as Maven artifacts and use them to produce the thin and fat servlet, full and other testsuite distributions. > The legacy servlet and full feature-packs should still be built. They could still be used to produce the legacy builds and distributions by activating Maven profiles. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10318) Use Galleon to build Wild full distributions

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFLY-10318?page=com.atlassian.jira.plugin... ] Alexey Loubyansky reassigned WFLY-10318: ---------------------------------------- Assignee: Brian Stansberry (was: Jason Greene) > Use Galleon to build Wild full distributions > -------------------------------------------- > > Key: WFLY-10318 > URL: https://issues.jboss.org/browse/WFLY-10318 > Project: WildFly > Issue Type: Task > Components: Server > Reporter: Alexey Loubyansky > Assignee: Brian Stansberry > > Switch from the current feature-pack-based provisioning to Galleon and WildFly Galleon plugins. > Create galleon feature packs as Maven artifacts and use them to produce the thin and fat servlet, full and other testsuite distributions. > The legacy servlet and full feature-packs should still be built. They could still be used to produce the legacy builds and distributions by activating Maven profiles. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10318) Use Galleon to build Wild full distributions

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created WFLY-10318: ---------------------------------------- Summary: Use Galleon to build Wild full distributions Key: WFLY-10318 URL: https://issues.jboss.org/browse/WFLY-10318 Project: WildFly Issue Type: Task Components: Server Reporter: Alexey Loubyansky Assignee: Jason Greene Switch from the current build tools to the Galleon and WildFly Galleon plugins. Create galleon feature packs as Maven artifacts and use them to produce the thin and fat servlet, full and other testsuite distributions. The legacy servlet and full feature-packs should still be built. They could still be used to produce the legacy builds and distributions by activating Maven profiles. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2520) Fix handling of executors and threads in drools-compiler tests

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2520?page=com.atlassian.jira.plugi... ] Tibor Zimányi closed DROOLS-2520. --------------------------------- > Fix handling of executors and threads in drools-compiler tests > -------------------------------------------------------------- > > Key: DROOLS-2520 > URL: https://issues.jboss.org/browse/DROOLS-2520 > Project: Drools > Issue Type: Task > Components: core engine > Affects Versions: 7.7.0.Final > Reporter: Tibor Zimányi > Assignee: Tibor Zimányi > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9494) Remove jboss-ejb-client.properties and wildfly-config.xml from default locations in the test suite

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/WFLY-9494?page=com.atlassian.jira.plugin.... ] Yeray Borges commented on WFLY-9494: ------------------------------------ Correct [~dlofthouse], wildfly-config.xml files were removed from those locations: https://issues.jboss.org/browse/WFLY-8802, ejb-client properties are still there I haven't found a simple solution for this issue yet. > Remove jboss-ejb-client.properties and wildfly-config.xml from default locations in the test suite > -------------------------------------------------------------------------------------------------- > > Key: WFLY-9494 > URL: https://issues.jboss.org/browse/WFLY-9494 > Project: WildFly > Issue Type: Task > Components: EJB, Test Suite > Reporter: Yeray Borges > Assignee: Yeray Borges > > Currently, the test suite contains > {noformat} > testsuite/integration/basic/src/test/resources/jboss-ejb-client.properties > testsuite/integration/basic/src/test/resources/wildfly-config.xml > testsuite/integration/legacy-ejb-client/src/test/resources/jboss-ejb-client.properties > testsuite/integration/manualmode/src/test/resources/jboss-ejb-client.properties > {noformat} > This means that all {{@RunAsClient}} tests pick them up by default and it's very difficult to add new tests which need to use the same configuration files but with different contents than the default ones, without negatively affecting other tests. > For example, it's not easily possible to make a test completely ignore the {{jboss-ejb-client.properties}} because setting the {{jboss.ejb.client.properties.file.path}} property to an empty string still makes the EJB client use the file from the default location (it is possible to switch to a different valid {{jboss-ejb-client.properties}} but not to just tell the test to not use any at all). > No such file should be present in the location from which it is picked up by default, tests which need such file should set up paths to them (for example, using {{wildfly.config.url}} and {{jboss.ejb.client.properties.file.path}} system properties). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-9) Elytron permission-set should throw exception for non-existent permission

by Ondrej Lukas (JIRA)

Ondrej Lukas created WFWIP-9: -------------------------------- Summary: Elytron permission-set should throw exception for non-existent permission Key: WFWIP-9 URL: https://issues.jboss.org/browse/WFWIP-9 Project: WildFly WIP Issue Type: Bug Reporter: Ondrej Lukas Assignee: Farah Juma When non-existent permission (e.g. when there is a typo in class-name) is added to Elytron permission-set then exception should be thrown. It should throw exception for wrong class-name as well as wrong module. See issue WFCORE-3796 for more details. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 May 2018