May 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-1119) Update existing PR jobs and create new one for new operator repo

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1119?page=com.atlassian.jira.plugi... ] Filip Brychta resolved SWSQE-1119. ---------------------------------- Resolution: Done It was decided not to use automatic triggers for PR tests. It's possible to start the main pipeline for PR manually just by specifying correct PR number. > Update existing PR jobs and create new one for new operator repo > ---------------------------------------------------------------- > > Key: SWSQE-1119 > URL: https://issues.redhat.com/browse/SWSQE-1119 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFWIP-301) SingleServerRuntimeTest intermittent failure in CodeReady Studio jobs

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/WFWIP-301?page=com.atlassian.jira.plugin... ] Josef Kopriva commented on WFWIP-301: ------------------------------------- Yes, please use the newer one: eap-7.x-crs-compatibility-tools-latest-released > SingleServerRuntimeTest intermittent failure in CodeReady Studio jobs > --------------------------------------------------------------------- > > Key: WFWIP-301 > URL: https://issues.redhat.com/browse/WFWIP-301 > Project: WildFly WIP > Issue Type: Bug > Reporter: Marek Kopecky > Assignee: Josef Kopriva > Priority: Blocker > > [CodeReady Studio Jenkins jobs|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/vie...] is not stable. > I started this job a few times and it seems that there is intermittent failure of SingleServerRuntimeTest operate no-configuration test, see [this jenkins run|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view...] or [this run|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view...], both with EAP 7.3.0.GA.CR3. > EAP QE needs clear statement on behalf of JBDS QE Team whether "this test failure doesn't block EAP7-1128 RFE and can be ignored" or let me know when the job will be stable. Until that, I consider that the job is not ready and blocks EAP7-1128 RFE. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-1157) Automate Peer|Request Authentication creation

by Hayk Hovsepyan (Jira)

Hayk Hovsepyan created SWSQE-1157: ------------------------------------- Summary: Automate Peer|Request Authentication creation Key: SWSQE-1157 URL: https://issues.redhat.com/browse/SWSQE-1157 Project: Kiali QE Issue Type: QE Task Reporter: Hayk Hovsepyan https://github.com/kiali/kiali-ui/pull/1804 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10173) EjbInvocationStatisticsTestCase fails on Windows: wait-time=0

by Lukas Vydra (Jira)

[ https://issues.redhat.com/browse/WFLY-10173?page=com.atlassian.jira.plugi... ] Lukas Vydra edited comment on WFLY-10173 at 5/21/20 7:41 AM: ------------------------------------------------------------- Hi [~cfang], I have been testing it and it seems that simply extending waiting time doesn't solve the problem, at least not on Windows. It seems that the problem is somewhere deeper. was (Author: lvydra): Hi [~cfang], I have been testing it and it seems that simply extending waiting time doesn't solve the problem, at least not on Windows. > EjbInvocationStatisticsTestCase fails on Windows: wait-time=0 > ------------------------------------------------------------- > > Key: WFLY-10173 > URL: https://issues.redhat.com/browse/WFLY-10173 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 12.0.0.Final > Reporter: Jan Kalina > Assignee: Cheng Fang > Priority: Major > Fix For: 20.0.0.Final > > > Sometime, when running EjbInvocationStatisticsTestCase on Windows, assertion fails, as wait-time is 0 (verified it is 0 by adding debug message). > For me it fails allTests in most of cases, but when running test standalone, it fails only in 1 of 4 cases. > I suppose it is because of too short sleep in AbstractManagedBean. (in test is called 4 times, each invocation include 50ms sleep, so I consider probable the wait-time is 0 - need to use longer sleeps to fulfill the test) > {code} > [ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.078 s <<< FAILURE! - in org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase > [ERROR] testSingletonWaitTime(org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase) Time elapsed: 0.438 s <<< FAILURE! > java.lang.AssertionError > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase.validateWaitTimeStatistic(EjbInvocationStatisticsTestCase.java:179) > at org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase.testSingletonWaitTime(EjbInvocationStatisticsTestCase.java:148) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:564) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at org.jboss.arquillian.junit.Arquillian$8$1.invoke(Arquillian.java:379) > ... > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10173) EjbInvocationStatisticsTestCase fails on Windows: wait-time=0

by Lukas Vydra (Jira)

[ https://issues.redhat.com/browse/WFLY-10173?page=com.atlassian.jira.plugi... ] Lukas Vydra commented on WFLY-10173: ------------------------------------ Hi [~cfang], I have been testing it and it seems that simply extending waiting time doesn't solve the problem, at least not on Windows. > EjbInvocationStatisticsTestCase fails on Windows: wait-time=0 > ------------------------------------------------------------- > > Key: WFLY-10173 > URL: https://issues.redhat.com/browse/WFLY-10173 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 12.0.0.Final > Reporter: Jan Kalina > Assignee: Cheng Fang > Priority: Major > Fix For: 20.0.0.Final > > > Sometime, when running EjbInvocationStatisticsTestCase on Windows, assertion fails, as wait-time is 0 (verified it is 0 by adding debug message). > For me it fails allTests in most of cases, but when running test standalone, it fails only in 1 of 4 cases. > I suppose it is because of too short sleep in AbstractManagedBean. (in test is called 4 times, each invocation include 50ms sleep, so I consider probable the wait-time is 0 - need to use longer sleeps to fulfill the test) > {code} > [ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.078 s <<< FAILURE! - in org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase > [ERROR] testSingletonWaitTime(org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase) Time elapsed: 0.438 s <<< FAILURE! > java.lang.AssertionError > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase.validateWaitTimeStatistic(EjbInvocationStatisticsTestCase.java:179) > at org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase.testSingletonWaitTime(EjbInvocationStatisticsTestCase.java:148) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:564) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at org.jboss.arquillian.junit.Arquillian$8$1.invoke(Arquillian.java:379) > ... > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12936) Provide ability to configure HTTP/2 (requires TLSv1.2) in FIPS mode (PKCS11)

by Diana Vilkolakova (Jira)

[ https://issues.redhat.com/browse/WFLY-12936?page=com.atlassian.jira.plugi... ] Diana Vilkolakova closed WFLY-12936. ------------------------------------ Resolution: Rejected Closing this issue as we consider certifications such as FIPS in relation to EAP only so we don't publish community analysis documents or community documentation for FIPS features > Provide ability to configure HTTP/2 (requires TLSv1.2) in FIPS mode (PKCS11) > ---------------------------------------------------------------------------- > > Key: WFLY-12936 > URL: https://issues.redhat.com/browse/WFLY-12936 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: Diana Vilkolakova > Assignee: Diana Vilkolakova > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5357) DROOLS-5356

by Dmitrii Tikhomirov (Jira)

Dmitrii Tikhomirov created DROOLS-5357: ------------------------------------------ Summary: DROOLS-5356 Key: DROOLS-5357 URL: https://issues.redhat.com/browse/DROOLS-5357 Project: Drools Issue Type: Feature Request Reporter: Dmitrii Tikhomirov Assignee: Mario Fusco -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5356) port bigmath to gwt2

by Dmitrii Tikhomirov (Jira)

Dmitrii Tikhomirov created DROOLS-5356: ------------------------------------------ Summary: port bigmath to gwt2 Key: DROOLS-5356 URL: https://issues.redhat.com/browse/DROOLS-5356 Project: Drools Issue Type: Feature Request Reporter: Dmitrii Tikhomirov Assignee: Dmitrii Tikhomirov -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5355) DROOLS-5354

by Dmitrii Tikhomirov (Jira)

Dmitrii Tikhomirov created DROOLS-5355: ------------------------------------------ Summary: DROOLS-5354 Key: DROOLS-5355 URL: https://issues.redhat.com/browse/DROOLS-5355 Project: Drools Issue Type: Feature Request Reporter: Dmitrii Tikhomirov Assignee: Mario Fusco -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5354) port javax.nio to gwt2

by Dmitrii Tikhomirov (Jira)

Dmitrii Tikhomirov created DROOLS-5354: ------------------------------------------ Summary: port javax.nio to gwt2 Key: DROOLS-5354 URL: https://issues.redhat.com/browse/DROOLS-5354 Project: Drools Issue Type: Feature Request Reporter: Dmitrii Tikhomirov Assignee: Toni Rikkola -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 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 May 2020