[JBoss JIRA] (WFLY-11718) MicroProfileMetricsHistogramMultipleInvocationsTestCase fails intermittently
by Chao Wang (Jira)
[ https://issues.jboss.org/browse/WFLY-11718?page=com.atlassian.jira.plugin... ]
Chao Wang commented on WFLY-11718:
----------------------------------
This can be produced 100% in slow invocation (break point or time waiting among invocations).
I think this happens due to the smallrye-metrics [ExponentiallyDecayingReservoir|https://github.com/smallrye/smallrye-metri...] implementation as explained
{code:java}
/**
* Creates a new {@link ExponentiallyDecayingReservoir} of 1028 elements, which offers a 99.9%
* confidence level with a 5% margin of error assuming a normal distribution, and an alpha
* factor of 0.015, which heavily biases the reservoir to the past 5 minutes of measurements.
*/
{code}
which updates item weight based on time calculation
{code:java}
final double itemWeight = weight(timestamp - startTime);
{code}
So this will eventually affect weighted arithmetic mean result.
[ExportersMetricScalingTest.histogram_json|https://github.com/smallrye/sma...] calls assertEquals with a delta value at the end as:
{code:java}
assertEquals(120.0, json.getJsonNumber("mean").doubleValue(), 0.001);
{code}
Last two teamcity failures are:
{noformat}
java.lang.AssertionError: Expected value of 'mean' is 3.0, but was 3.0089998312537976.
java.lang.AssertionError: Expected value of 'mean' is 3.0, but was 3.007477427516212.
{noformat}
[~jmesnil] Can we add an acceptable delta as well for this?
> MicroProfileMetricsHistogramMultipleInvocationsTestCase fails intermittently
> ----------------------------------------------------------------------------
>
> Key: WFLY-11718
> URL: https://issues.jboss.org/browse/WFLY-11718
> Project: WildFly
> Issue Type: Bug
> Components: MP Metrics
> Affects Versions: 16.0.0.Beta1
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Priority: Major
>
> Test org.wildfly.test.integration.microprofile.metrics.metadata.MicroProfileMetricsHistogramMultipleInvocationsTestCase.testMultipleInvocationsOfEndpoint is failing intermittently.
> @Ignore-it until it is fix to consistently pass.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11739) Transaction JDBC object store does not start on PostgreSQL Plus 10.1
by Tom Jenkinson (Jira)
[ https://issues.jboss.org/browse/WFLY-11739?page=com.atlassian.jira.plugin... ]
Tom Jenkinson updated WFLY-11739:
---------------------------------
Priority: Major (was: Blocker)
> Transaction JDBC object store does not start on PostgreSQL Plus 10.1
> --------------------------------------------------------------------
>
> Key: WFLY-11739
> URL: https://issues.jboss.org/browse/WFLY-11739
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 14.0.0.Final, 15.0.1.Final, 16.0.0.Beta1
> Reporter: Ivan Straka
> Assignee: Ivan Straka
> Priority: Major
>
> The JBossTM has not got driver class for PostgreSQL Plus 10.1. This results in a _ClassNotFoundException_ exception when transaction subsystem is configured to use a JDBC transaction object store on PostgreSQL Plus 10.1.
> The problem is that there is no driver class in [this package|https://github.com/jbosstm/narayana/tree/5.9.1.Final/ArjunaCore/a...] for [edb-jdbc18.jar|http://www.qa.jboss.com/jdbc-drivers-products/EAP/7.3.0/po...] which is supposed to be used for PostgreSQL Plus 10.1. Narayana expects _edb_driver_ class. This has changed since edb-jdbc17.jar where _postgresql_driver_ is expected.
> PostgreSQL Plus 10.1 is supported in 7.2.0 and 7.3.0, Customers can not used the DB as JDBC object store due to this issue.
> {code:java}
> 16:33:17,027 FATAL [com.arjuna.ats.arjuna] (MSC service thread 1-2) ARJUNA012260: Received exception for com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DataSourceJDBCAccess:JASDTJBossTSTxTable: java.lang.ClassNotFoundException: com.arjuna.ats.internal.arjuna.objectstore.jdbc.drivers.edb_driver from [Module "org.jboss.jts" from local module loader @2b80d80f (finder: local module finder @3ab39c39 (roots: /home/istraka/repositories/gitlab/tests-management/jboss-eap-7.1/modules,/home/istraka/repositories/gitlab/tests-management/jboss-eap-7.1/modules/system/layers/base))]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:198)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:412)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:400)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore.<init>(JDBCStore.java:251)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClass(ClassloadingUtility.java:129)
> at com.arjuna.ats.arjuna.objectstore.StoreManager.initStore(StoreManager.java:152)
> at com.arjuna.ats.arjuna.objectstore.StoreManager.getActionStore(StoreManager.java:111)
> at com.arjuna.ats.arjuna.objectstore.StoreManager.getRecoveryStore(StoreManager.java:68)
> at com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.<init>(CommitMarkableResourceRecordRecoveryModule.java:156)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClass(ClassloadingUtility.java:135)
> at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClassesWithInit(ClassloadingUtility.java:192)
> at com.arjuna.ats.arjuna.common.RecoveryEnvironmentBean.getRecoveryModules(RecoveryEnvironmentBean.java:465)
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.loadModules(PeriodicRecovery.java:883)
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.<init>(PeriodicRecovery.java:121)
> at com.arjuna.ats.internal.arjuna.recovery.RecoveryManagerImple.<init>(RecoveryManagerImple.java:107)
> at com.arjuna.ats.arjuna.recovery.RecoveryManager.<init>(RecoveryManager.java:477)
> at com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:132)
> at com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:112)
> at com.arjuna.ats.jbossatx.jta.RecoveryManagerService.create(RecoveryManagerService.java:54)
> at org.jboss.as.txn.service.ArjunaRecoveryManagerService.start(ArjunaRecoveryManagerService.java:126)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11739) Transaction JDBC object store does not start on PostgreSQL Plus 10.1
by Tom Jenkinson (Jira)
[ https://issues.jboss.org/browse/WFLY-11739?page=com.atlassian.jira.plugin... ]
Tom Jenkinson reassigned WFLY-11739:
------------------------------------
Assignee: Ivan Straka (was: Tom Jenkinson)
> Transaction JDBC object store does not start on PostgreSQL Plus 10.1
> --------------------------------------------------------------------
>
> Key: WFLY-11739
> URL: https://issues.jboss.org/browse/WFLY-11739
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 14.0.0.Final, 15.0.1.Final, 16.0.0.Beta1
> Reporter: Ivan Straka
> Assignee: Ivan Straka
> Priority: Blocker
>
> The JBossTM has not got driver class for PostgreSQL Plus 10.1. This results in a _ClassNotFoundException_ exception when transaction subsystem is configured to use a JDBC transaction object store on PostgreSQL Plus 10.1.
> The problem is that there is no driver class in [this package|https://github.com/jbosstm/narayana/tree/5.9.1.Final/ArjunaCore/a...] for [edb-jdbc18.jar|http://www.qa.jboss.com/jdbc-drivers-products/EAP/7.3.0/po...] which is supposed to be used for PostgreSQL Plus 10.1. Narayana expects _edb_driver_ class. This has changed since edb-jdbc17.jar where _postgresql_driver_ is expected.
> PostgreSQL Plus 10.1 is supported in 7.2.0 and 7.3.0, Customers can not used the DB as JDBC object store due to this issue.
> {code:java}
> 16:33:17,027 FATAL [com.arjuna.ats.arjuna] (MSC service thread 1-2) ARJUNA012260: Received exception for com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DataSourceJDBCAccess:JASDTJBossTSTxTable: java.lang.ClassNotFoundException: com.arjuna.ats.internal.arjuna.objectstore.jdbc.drivers.edb_driver from [Module "org.jboss.jts" from local module loader @2b80d80f (finder: local module finder @3ab39c39 (roots: /home/istraka/repositories/gitlab/tests-management/jboss-eap-7.1/modules,/home/istraka/repositories/gitlab/tests-management/jboss-eap-7.1/modules/system/layers/base))]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:198)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:412)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:400)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore.<init>(JDBCStore.java:251)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClass(ClassloadingUtility.java:129)
> at com.arjuna.ats.arjuna.objectstore.StoreManager.initStore(StoreManager.java:152)
> at com.arjuna.ats.arjuna.objectstore.StoreManager.getActionStore(StoreManager.java:111)
> at com.arjuna.ats.arjuna.objectstore.StoreManager.getRecoveryStore(StoreManager.java:68)
> at com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.<init>(CommitMarkableResourceRecordRecoveryModule.java:156)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClass(ClassloadingUtility.java:135)
> at com.arjuna.common.internal.util.ClassloadingUtility.loadAndInstantiateClassesWithInit(ClassloadingUtility.java:192)
> at com.arjuna.ats.arjuna.common.RecoveryEnvironmentBean.getRecoveryModules(RecoveryEnvironmentBean.java:465)
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.loadModules(PeriodicRecovery.java:883)
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.<init>(PeriodicRecovery.java:121)
> at com.arjuna.ats.internal.arjuna.recovery.RecoveryManagerImple.<init>(RecoveryManagerImple.java:107)
> at com.arjuna.ats.arjuna.recovery.RecoveryManager.<init>(RecoveryManager.java:477)
> at com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:132)
> at com.arjuna.ats.arjuna.recovery.RecoveryManager.manager(RecoveryManager.java:112)
> at com.arjuna.ats.jbossatx.jta.RecoveryManagerService.create(RecoveryManagerService.java:54)
> at org.jboss.as.txn.service.ArjunaRecoveryManagerService.start(ArjunaRecoveryManagerService.java:126)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (SWSQE-617) Migrate our test ocp clusters to PSI
by Filip Brychta (Jira)
Filip Brychta created SWSQE-617:
-----------------------------------
Summary: Migrate our test ocp clusters to PSI
Key: SWSQE-617
URL: https://issues.jboss.org/browse/SWSQE-617
Project: Kiali QE
Issue Type: Sub-task
Reporter: Filip Brychta
Assignee: Filip Brychta
We need to answer following questions:
* do we want to do that or stay in our bos lab
* how to provision ocp clusters in PSI (Flexy? Flexy wrapper, LInchpin)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (SWSQE-616) Migrate our jenkins slaves to PSI
by Filip Brychta (Jira)
Filip Brychta created SWSQE-616:
-----------------------------------
Summary: Migrate our jenkins slaves to PSI
Key: SWSQE-616
URL: https://issues.jboss.org/browse/SWSQE-616
Project: Kiali QE
Issue Type: Sub-task
Reporter: Filip Brychta
Assignee: Filip Brychta
Before we do the migration we need to answer following questions:
* do we want to use containers for jenkins slaves in ocp or VMs in openStack?
* currently we need privileged containers (for kiali-build), is it possible to have it in PSI?
* check connectivity (stability/latency) to our testing ocp clusters (in our bos lab and in PSI)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (SWSQE-605) Establish Central CI Jenkins Master For Kiali
by Filip Brychta (Jira)
[ https://issues.jboss.org/browse/SWSQE-605?page=com.atlassian.jira.plugin.... ]
Filip Brychta updated SWSQE-605:
--------------------------------
Description:
Our team at one time was allocated a Central CI Jenkins Master.
Therefore, one of the following,
Either:
a) Confirm that our team's Central CI Jenkins Master is still available and usable
Or
b) Establish a new Central CI Jenkins Master
We also need to confirm that Jenkins master in Central Ci will fit our needs like:
* is it possible to run smee.io client there to consume github events
* is it possible to install plugins we are using
* check SLA
* check backups, upgrades
* do we want to share it with istio qe team?
was:
Our team at one time was allocated a Central CI Jenkins Master.
Therefore, one of the following,
Either:
a) Confirm that our team's Central CI Jenkins Master is still available and usable
Or
b) Establish a new Central CI Jenkins Master
We also need to confirm that Jenkins master in Central Ci will fit our needs like:
* is it possible to run smee.io client there to consume github events
* is it possible to install plugins we are using
* check SLA
* check backups, upgrades
> Establish Central CI Jenkins Master For Kiali
> ---------------------------------------------
>
> Key: SWSQE-605
> URL: https://issues.jboss.org/browse/SWSQE-605
> Project: Kiali QE
> Issue Type: Sub-task
> Reporter: Matt Mahoney
> Assignee: Matt Mahoney
> Priority: Major
>
> Our team at one time was allocated a Central CI Jenkins Master.
> Therefore, one of the following,
> Either:
> a) Confirm that our team's Central CI Jenkins Master is still available and usable
> Or
> b) Establish a new Central CI Jenkins Master
> We also need to confirm that Jenkins master in Central Ci will fit our needs like:
> * is it possible to run smee.io client there to consume github events
> * is it possible to install plugins we are using
> * check SLA
> * check backups, upgrades
> * do we want to share it with istio qe team?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (SWSQE-605) Establish Central CI Jenkins Master For Kiali
by Filip Brychta (Jira)
[ https://issues.jboss.org/browse/SWSQE-605?page=com.atlassian.jira.plugin.... ]
Filip Brychta updated SWSQE-605:
--------------------------------
Description:
Our team at one time was allocated a Central CI Jenkins Master.
Therefore, one of the following,
Either:
a) Confirm that our team's Central CI Jenkins Master is still available and usable
Or
b) Establish a new Central CI Jenkins Master
We also need to confirm that Jenkins master in Central Ci will fit our needs like:
* is it possible to run smee.io client there to consume github events
* is it possible to install plugins we are using
* check SLA
* check backups, upgrades
was:
Our team at one time was allocated a Central CI Jenkins Master.
Therefore, one of the following,
Either:
a) Confirm that our team's Central CI Jenkins Master is still available and usable
Or
b) Establish a new Central CI Jenkins Master
> Establish Central CI Jenkins Master For Kiali
> ---------------------------------------------
>
> Key: SWSQE-605
> URL: https://issues.jboss.org/browse/SWSQE-605
> Project: Kiali QE
> Issue Type: Sub-task
> Reporter: Matt Mahoney
> Assignee: Matt Mahoney
> Priority: Major
>
> Our team at one time was allocated a Central CI Jenkins Master.
> Therefore, one of the following,
> Either:
> a) Confirm that our team's Central CI Jenkins Master is still available and usable
> Or
> b) Establish a new Central CI Jenkins Master
> We also need to confirm that Jenkins master in Central Ci will fit our needs like:
> * is it possible to run smee.io client there to consume github events
> * is it possible to install plugins we are using
> * check SLA
> * check backups, upgrades
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months