Timeout errors in JCA bits in testsuite

classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

Timeout errors in JCA bits in testsuite

Brian Stansberry
In the last day I've seen 3 different CI runs fail due to various JCA
related tests in testsuite/basic not completing. Does anyone have any
idea what might be causing this?

The ones I noticed were all PR tests of changes in core. It's hard to
imagine the PRs themselves were relevant. They do test a snapshot of
core though, so it's possible some change in core is relevant, in
addition to the simpler scenario of some issue in full.

1) Just now:

http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildTypeId=WildFlyCore_PullRequest_WildFlyCoreFullIntegration&buildId=87619

[22:05:58][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.moduledeployment.BasicFlatTestCase
[22:06:00][org.wildfly:wildfly-ts-integ-basic] Tests run: 4, Failures:
0, Errors: 0, Skipped: 0, Time elapsed: 2.084 sec - in
org.jboss.as.test.integration.jca.moduledeployment.BasicFlatTestCase
[22:06:00][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.moduledeployment.BasicJarTestCase
[22:06:02][org.wildfly:wildfly-ts-integ-basic] Tests run: 4, Failures:
0, Errors: 0, Skipped: 0, Time elapsed: 1.598 sec - in
org.jboss.as.test.integration.jca.moduledeployment.BasicJarTestCase
[22:06:02][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.moduledeployment.InflowFlatTestCase
[22:30:48][org.wildfly:wildfly-ts-integ-basic]
[22:30:48][org.wildfly:wildfly-ts-integ-basic] Results :
[22:30:48][org.wildfly:wildfly-ts-integ-basic]
[22:30:48][org.wildfly:wildfly-ts-integ-basic] Tests run: 8, Failures:
0, Errors: 0, Skipped: 0
[22:30:48][org.wildfly:wildfly-ts-integ-basic]
[22:30:48][org.wildfly:wildfly-ts-integ-basic] [ERROR] There was a
timeout or other error in the fork

2) Yesterday:

http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=87585&tab=buildResultsDiv&buildTypeId=WF_WildFlyCoreIntegrationExperiments

[14:48:42][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.beanvalidation.PositiveValidationTestCase
[14:48:43][org.wildfly:wildfly-ts-integ-basic] Tests run: 3, Failures:
0, Errors: 0, Skipped: 0, Time elapsed: 0.669 sec - in
org.jboss.as.test.integration.jca.beanvalidation.PositiveValidationTestCase
[14:48:43][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.capacitypolicies.DatasourceCapacityPoliciesTestCase
[14:48:44][org.wildfly:wildfly-ts-integ-basic] Tests run: 1, Failures:
0, Errors: 0, Skipped: 0, Time elapsed: 0.98 sec - in
org.jboss.as.test.integration.jca.capacitypolicies.DatasourceCapacityPoliciesTestCase
[14:48:44][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.capacitypolicies.ResourceAdapterCapacityPoliciesTestCase
[14:48:44][org.wildfly:wildfly-ts-integ-basic] Tests run: 1, Failures:
0, Errors: 0, Skipped: 0, Time elapsed: 0.766 sec - in
org.jboss.as.test.integration.jca.capacitypolicies.ResourceAdapterCapacityPoliciesTestCase
[14:48:44][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.capacitypolicies.XADatasourceCapacityPoliciesTestCase
[14:48:45][org.wildfly:wildfly-ts-integ-basic] Tests run: 1, Failures:
0, Errors: 0, Skipped: 0, Time elapsed: 0.718 sec - in
org.jboss.as.test.integration.jca.capacitypolicies.XADatasourceCapacityPoliciesTestCase
[14:48:45][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.datasource.DatasourceEnableAttributeTestCase
[14:48:51][org.wildfly:wildfly-ts-integ-basic] Tests run: 6, Failures:
0, Errors: 0, Skipped: 0, Time elapsed: 5.881 sec - in
org.jboss.as.test.integration.jca.datasource.DatasourceEnableAttributeTestCase
[14:48:51][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.datasource.DatasourceXaEnableAttributeTestCase
[15:07:51][org.wildfly:wildfly-ts-integ-basic]
[15:07:51][org.wildfly:wildfly-ts-integ-basic] Results :
[15:07:51][org.wildfly:wildfly-ts-integ-basic]
[15:07:51][org.wildfly:wildfly-ts-integ-basic] Tests run: 761, Failures:
0, Errors: 0, Skipped: 12
[15:07:51][org.wildfly:wildfly-ts-integ-basic]
[15:07:51][org.wildfly:wildfly-ts-integ-basic] [ERROR] There was a
timeout or other error in the fork

3) Yesterday:

http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=87425&tab=buildResultsDiv&buildTypeId=WF_WildFlyCoreIntegrationExperiments

[01:38:34][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.moduledeployment.BasicFlatTestCase
[01:38:36][org.wildfly:wildfly-ts-integ-basic] Tests run: 4, Failures:
0, Errors: 0, Skipped: 0, Time elapsed: 1.583 sec - in
org.jboss.as.test.integration.jca.moduledeployment.BasicFlatTestCase
[01:38:36][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.moduledeployment.BasicJarTestCase
[01:38:37][org.wildfly:wildfly-ts-integ-basic] Tests run: 4, Failures:
0, Errors: 0, Skipped: 0, Time elapsed: 1.215 sec - in
org.jboss.as.test.integration.jca.moduledeployment.BasicJarTestCase
[01:38:37][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.moduledeployment.InflowFlatTestCase
[01:38:38][org.wildfly:wildfly-ts-integ-basic] Tests run: 2, Failures:
0, Errors: 0, Skipped: 0, Time elapsed: 1.23 sec - in
org.jboss.as.test.integration.jca.moduledeployment.InflowFlatTestCase
[01:38:38][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.moduledeployment.InflowJarTestCase
[01:38:40][org.wildfly:wildfly-ts-integ-basic] Tests run: 2, Failures:
0, Errors: 0, Skipped: 0, Time elapsed: 1.086 sec - in
org.jboss.as.test.integration.jca.moduledeployment.InflowJarTestCase
[01:38:40][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.moduledeployment.MultiActivationFlatTestCase
[01:38:41][org.wildfly:wildfly-ts-integ-basic] Tests run: 7, Failures:
0, Errors: 0, Skipped: 0, Time elapsed: 1.165 sec - in
org.jboss.as.test.integration.jca.moduledeployment.MultiActivationFlatTestCase
[01:38:41][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.moduledeployment.MultiActivationJarTestCase
[01:38:42][org.wildfly:wildfly-ts-integ-basic] Tests run: 7, Failures:
0, Errors: 0, Skipped: 0, Time elapsed: 1.111 sec - in
org.jboss.as.test.integration.jca.moduledeployment.MultiActivationJarTestCase
[01:38:42][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.moduledeployment.MultiObjectActivationFlatTestCase
[01:38:43][org.wildfly:wildfly-ts-integ-basic] Tests run: 5, Failures:
0, Errors: 0, Skipped: 0, Time elapsed: 1.694 sec - in
org.jboss.as.test.integration.jca.moduledeployment.MultiObjectActivationFlatTestCase
[01:38:43][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.moduledeployment.MultiObjectActivationJarTestCase
[01:38:45][org.wildfly:wildfly-ts-integ-basic] Tests run: 5, Failures:
0, Errors: 0, Skipped: 0, Time elapsed: 1.24 sec - in
org.jboss.as.test.integration.jca.moduledeployment.MultiObjectActivationJarTestCase
[01:38:45][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.moduledeployment.PartialObjectActivationFlatTestCase
[02:03:26][org.wildfly:wildfly-ts-integ-basic]
[02:03:26][org.wildfly:wildfly-ts-integ-basic] Results :
[02:03:26][org.wildfly:wildfly-ts-integ-basic]
[02:03:26][org.wildfly:wildfly-ts-integ-basic] Tests run: 36, Failures:
0, Errors: 0, Skipped: 0
[02:03:26][org.wildfly:wildfly-ts-integ-basic]
[02:03:26][org.wildfly:wildfly-ts-integ-basic] [ERROR] There was a
timeout or other error in the fork

--
Brian Stansberry
Senior Principal Software Engineer
JBoss by Red Hat
_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: Timeout errors in JCA bits in testsuite

Eduardo Sant´Ana da Silva
Seems that this is related to maven, probably something its taking more time than due.


2016-01-27 20:55 GMT-02:00 Brian Stansberry <[hidden email]>:
In the last day I've seen 3 different CI runs fail due to various JCA
related tests in testsuite/basic not completing. Does anyone have any
idea what might be causing this?

The ones I noticed were all PR tests of changes in core. It's hard to
imagine the PRs themselves were relevant. They do test a snapshot of
core though, so it's possible some change in core is relevant, in
addition to the simpler scenario of some issue in full.

1) Just now:

http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildTypeId=WildFlyCore_PullRequest_WildFlyCoreFullIntegration&buildId=87619

[22:05:58][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.moduledeployment.BasicFlatTestCase
[22:06:00][org.wildfly:wildfly-ts-integ-basic] Tests run: 4, Failures:
0, Errors: 0, Skipped: 0, Time elapsed: 2.084 sec - in
org.jboss.as.test.integration.jca.moduledeployment.BasicFlatTestCase
[22:06:00][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.moduledeployment.BasicJarTestCase
[22:06:02][org.wildfly:wildfly-ts-integ-basic] Tests run: 4, Failures:
0, Errors: 0, Skipped: 0, Time elapsed: 1.598 sec - in
org.jboss.as.test.integration.jca.moduledeployment.BasicJarTestCase
[22:06:02][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.moduledeployment.InflowFlatTestCase
[22:30:48][org.wildfly:wildfly-ts-integ-basic]
[22:30:48][org.wildfly:wildfly-ts-integ-basic] Results :
[22:30:48][org.wildfly:wildfly-ts-integ-basic]
[22:30:48][org.wildfly:wildfly-ts-integ-basic] Tests run: 8, Failures:
0, Errors: 0, Skipped: 0
[22:30:48][org.wildfly:wildfly-ts-integ-basic]
[22:30:48][org.wildfly:wildfly-ts-integ-basic] [ERROR] There was a
timeout or other error in the fork

2) Yesterday:

http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=87585&tab=buildResultsDiv&buildTypeId=WF_WildFlyCoreIntegrationExperiments

[14:48:42][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.beanvalidation.PositiveValidationTestCase
[14:48:43][org.wildfly:wildfly-ts-integ-basic] Tests run: 3, Failures:
0, Errors: 0, Skipped: 0, Time elapsed: 0.669 sec - in
org.jboss.as.test.integration.jca.beanvalidation.PositiveValidationTestCase
[14:48:43][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.capacitypolicies.DatasourceCapacityPoliciesTestCase
[14:48:44][org.wildfly:wildfly-ts-integ-basic] Tests run: 1, Failures:
0, Errors: 0, Skipped: 0, Time elapsed: 0.98 sec - in
org.jboss.as.test.integration.jca.capacitypolicies.DatasourceCapacityPoliciesTestCase
[14:48:44][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.capacitypolicies.ResourceAdapterCapacityPoliciesTestCase
[14:48:44][org.wildfly:wildfly-ts-integ-basic] Tests run: 1, Failures:
0, Errors: 0, Skipped: 0, Time elapsed: 0.766 sec - in
org.jboss.as.test.integration.jca.capacitypolicies.ResourceAdapterCapacityPoliciesTestCase
[14:48:44][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.capacitypolicies.XADatasourceCapacityPoliciesTestCase
[14:48:45][org.wildfly:wildfly-ts-integ-basic] Tests run: 1, Failures:
0, Errors: 0, Skipped: 0, Time elapsed: 0.718 sec - in
org.jboss.as.test.integration.jca.capacitypolicies.XADatasourceCapacityPoliciesTestCase
[14:48:45][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.datasource.DatasourceEnableAttributeTestCase
[14:48:51][org.wildfly:wildfly-ts-integ-basic] Tests run: 6, Failures:
0, Errors: 0, Skipped: 0, Time elapsed: 5.881 sec - in
org.jboss.as.test.integration.jca.datasource.DatasourceEnableAttributeTestCase
[14:48:51][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.datasource.DatasourceXaEnableAttributeTestCase
[15:07:51][org.wildfly:wildfly-ts-integ-basic]
[15:07:51][org.wildfly:wildfly-ts-integ-basic] Results :
[15:07:51][org.wildfly:wildfly-ts-integ-basic]
[15:07:51][org.wildfly:wildfly-ts-integ-basic] Tests run: 761, Failures:
0, Errors: 0, Skipped: 12
[15:07:51][org.wildfly:wildfly-ts-integ-basic]
[15:07:51][org.wildfly:wildfly-ts-integ-basic] [ERROR] There was a
timeout or other error in the fork

3) Yesterday:

http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=87425&tab=buildResultsDiv&buildTypeId=WF_WildFlyCoreIntegrationExperiments

[01:38:34][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.moduledeployment.BasicFlatTestCase
[01:38:36][org.wildfly:wildfly-ts-integ-basic] Tests run: 4, Failures:
0, Errors: 0, Skipped: 0, Time elapsed: 1.583 sec - in
org.jboss.as.test.integration.jca.moduledeployment.BasicFlatTestCase
[01:38:36][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.moduledeployment.BasicJarTestCase
[01:38:37][org.wildfly:wildfly-ts-integ-basic] Tests run: 4, Failures:
0, Errors: 0, Skipped: 0, Time elapsed: 1.215 sec - in
org.jboss.as.test.integration.jca.moduledeployment.BasicJarTestCase
[01:38:37][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.moduledeployment.InflowFlatTestCase
[01:38:38][org.wildfly:wildfly-ts-integ-basic] Tests run: 2, Failures:
0, Errors: 0, Skipped: 0, Time elapsed: 1.23 sec - in
org.jboss.as.test.integration.jca.moduledeployment.InflowFlatTestCase
[01:38:38][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.moduledeployment.InflowJarTestCase
[01:38:40][org.wildfly:wildfly-ts-integ-basic] Tests run: 2, Failures:
0, Errors: 0, Skipped: 0, Time elapsed: 1.086 sec - in
org.jboss.as.test.integration.jca.moduledeployment.InflowJarTestCase
[01:38:40][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.moduledeployment.MultiActivationFlatTestCase
[01:38:41][org.wildfly:wildfly-ts-integ-basic] Tests run: 7, Failures:
0, Errors: 0, Skipped: 0, Time elapsed: 1.165 sec - in
org.jboss.as.test.integration.jca.moduledeployment.MultiActivationFlatTestCase
[01:38:41][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.moduledeployment.MultiActivationJarTestCase
[01:38:42][org.wildfly:wildfly-ts-integ-basic] Tests run: 7, Failures:
0, Errors: 0, Skipped: 0, Time elapsed: 1.111 sec - in
org.jboss.as.test.integration.jca.moduledeployment.MultiActivationJarTestCase
[01:38:42][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.moduledeployment.MultiObjectActivationFlatTestCase
[01:38:43][org.wildfly:wildfly-ts-integ-basic] Tests run: 5, Failures:
0, Errors: 0, Skipped: 0, Time elapsed: 1.694 sec - in
org.jboss.as.test.integration.jca.moduledeployment.MultiObjectActivationFlatTestCase
[01:38:43][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.moduledeployment.MultiObjectActivationJarTestCase
[01:38:45][org.wildfly:wildfly-ts-integ-basic] Tests run: 5, Failures:
0, Errors: 0, Skipped: 0, Time elapsed: 1.24 sec - in
org.jboss.as.test.integration.jca.moduledeployment.MultiObjectActivationJarTestCase
[01:38:45][org.wildfly:wildfly-ts-integ-basic] Running
org.jboss.as.test.integration.jca.moduledeployment.PartialObjectActivationFlatTestCase
[02:03:26][org.wildfly:wildfly-ts-integ-basic]
[02:03:26][org.wildfly:wildfly-ts-integ-basic] Results :
[02:03:26][org.wildfly:wildfly-ts-integ-basic]
[02:03:26][org.wildfly:wildfly-ts-integ-basic] Tests run: 36, Failures:
0, Errors: 0, Skipped: 0
[02:03:26][org.wildfly:wildfly-ts-integ-basic]
[02:03:26][org.wildfly:wildfly-ts-integ-basic] [ERROR] There was a
timeout or other error in the fork

--
Brian Stansberry
Senior Principal Software Engineer
JBoss by Red Hat
_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev



--
__________________________
Eduardo Sant'Ana da Silva - Dr.
Pesquisador / Consultor de TI


_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: Timeout errors in JCA bits in testsuite

Carlo de Wolf
In reply to this post by Brian Stansberry
There should be no SNAPSHOT dependencies in any CI build. While it does build core beforehand, it might get overwritten by another CI run.
[org.wildfly.core:wildfly-core-parent] [INFO] Installing /opt/buildAgent/work/db872761b443af46/core/pom.xml to /store/repository/org/wildfly/core/wildfly-core-parent/2.0.8.Final-SNAPSHOT/wildfly-core-parent-2.0.8.Final-SNAPSHOT.pom

Would it be possible to use timed snapshots instead?

Carlo

On 01/27/2016 11:55 PM, Brian Stansberry wrote:
In the last day I've seen 3 different CI runs fail due to various JCA 
related tests in testsuite/basic not completing. Does anyone have any 
idea what might be causing this?

The ones I noticed were all PR tests of changes in core. It's hard to 
imagine the PRs themselves were relevant. They do test a snapshot of 
core though, so it's possible some change in core is relevant, in 
addition to the simpler scenario of some issue in full.

1) Just now:

http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildTypeId=WildFlyCore_PullRequest_WildFlyCoreFullIntegration&buildId=87619

[22:05:58][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.moduledeployment.BasicFlatTestCase
[22:06:00][org.wildfly:wildfly-ts-integ-basic] Tests run: 4, Failures: 
0, Errors: 0, Skipped: 0, Time elapsed: 2.084 sec - in 
org.jboss.as.test.integration.jca.moduledeployment.BasicFlatTestCase
[22:06:00][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.moduledeployment.BasicJarTestCase
[22:06:02][org.wildfly:wildfly-ts-integ-basic] Tests run: 4, Failures: 
0, Errors: 0, Skipped: 0, Time elapsed: 1.598 sec - in 
org.jboss.as.test.integration.jca.moduledeployment.BasicJarTestCase
[22:06:02][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.moduledeployment.InflowFlatTestCase
[22:30:48][org.wildfly:wildfly-ts-integ-basic]
[22:30:48][org.wildfly:wildfly-ts-integ-basic] Results :
[22:30:48][org.wildfly:wildfly-ts-integ-basic]
[22:30:48][org.wildfly:wildfly-ts-integ-basic] Tests run: 8, Failures: 
0, Errors: 0, Skipped: 0
[22:30:48][org.wildfly:wildfly-ts-integ-basic]
[22:30:48][org.wildfly:wildfly-ts-integ-basic] [ERROR] There was a 
timeout or other error in the fork

2) Yesterday:

http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=87585&tab=buildResultsDiv&buildTypeId=WF_WildFlyCoreIntegrationExperiments

[14:48:42][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.beanvalidation.PositiveValidationTestCase
[14:48:43][org.wildfly:wildfly-ts-integ-basic] Tests run: 3, Failures: 
0, Errors: 0, Skipped: 0, Time elapsed: 0.669 sec - in 
org.jboss.as.test.integration.jca.beanvalidation.PositiveValidationTestCase
[14:48:43][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.capacitypolicies.DatasourceCapacityPoliciesTestCase
[14:48:44][org.wildfly:wildfly-ts-integ-basic] Tests run: 1, Failures: 
0, Errors: 0, Skipped: 0, Time elapsed: 0.98 sec - in 
org.jboss.as.test.integration.jca.capacitypolicies.DatasourceCapacityPoliciesTestCase
[14:48:44][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.capacitypolicies.ResourceAdapterCapacityPoliciesTestCase
[14:48:44][org.wildfly:wildfly-ts-integ-basic] Tests run: 1, Failures: 
0, Errors: 0, Skipped: 0, Time elapsed: 0.766 sec - in 
org.jboss.as.test.integration.jca.capacitypolicies.ResourceAdapterCapacityPoliciesTestCase
[14:48:44][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.capacitypolicies.XADatasourceCapacityPoliciesTestCase
[14:48:45][org.wildfly:wildfly-ts-integ-basic] Tests run: 1, Failures: 
0, Errors: 0, Skipped: 0, Time elapsed: 0.718 sec - in 
org.jboss.as.test.integration.jca.capacitypolicies.XADatasourceCapacityPoliciesTestCase
[14:48:45][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.datasource.DatasourceEnableAttributeTestCase
[14:48:51][org.wildfly:wildfly-ts-integ-basic] Tests run: 6, Failures: 
0, Errors: 0, Skipped: 0, Time elapsed: 5.881 sec - in 
org.jboss.as.test.integration.jca.datasource.DatasourceEnableAttributeTestCase
[14:48:51][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.datasource.DatasourceXaEnableAttributeTestCase
[15:07:51][org.wildfly:wildfly-ts-integ-basic]
[15:07:51][org.wildfly:wildfly-ts-integ-basic] Results :
[15:07:51][org.wildfly:wildfly-ts-integ-basic]
[15:07:51][org.wildfly:wildfly-ts-integ-basic] Tests run: 761, Failures: 
0, Errors: 0, Skipped: 12
[15:07:51][org.wildfly:wildfly-ts-integ-basic]
[15:07:51][org.wildfly:wildfly-ts-integ-basic] [ERROR] There was a 
timeout or other error in the fork

3) Yesterday:

http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=87425&tab=buildResultsDiv&buildTypeId=WF_WildFlyCoreIntegrationExperiments

[01:38:34][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.moduledeployment.BasicFlatTestCase
[01:38:36][org.wildfly:wildfly-ts-integ-basic] Tests run: 4, Failures: 
0, Errors: 0, Skipped: 0, Time elapsed: 1.583 sec - in 
org.jboss.as.test.integration.jca.moduledeployment.BasicFlatTestCase
[01:38:36][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.moduledeployment.BasicJarTestCase
[01:38:37][org.wildfly:wildfly-ts-integ-basic] Tests run: 4, Failures: 
0, Errors: 0, Skipped: 0, Time elapsed: 1.215 sec - in 
org.jboss.as.test.integration.jca.moduledeployment.BasicJarTestCase
[01:38:37][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.moduledeployment.InflowFlatTestCase
[01:38:38][org.wildfly:wildfly-ts-integ-basic] Tests run: 2, Failures: 
0, Errors: 0, Skipped: 0, Time elapsed: 1.23 sec - in 
org.jboss.as.test.integration.jca.moduledeployment.InflowFlatTestCase
[01:38:38][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.moduledeployment.InflowJarTestCase
[01:38:40][org.wildfly:wildfly-ts-integ-basic] Tests run: 2, Failures: 
0, Errors: 0, Skipped: 0, Time elapsed: 1.086 sec - in 
org.jboss.as.test.integration.jca.moduledeployment.InflowJarTestCase
[01:38:40][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.moduledeployment.MultiActivationFlatTestCase
[01:38:41][org.wildfly:wildfly-ts-integ-basic] Tests run: 7, Failures: 
0, Errors: 0, Skipped: 0, Time elapsed: 1.165 sec - in 
org.jboss.as.test.integration.jca.moduledeployment.MultiActivationFlatTestCase
[01:38:41][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.moduledeployment.MultiActivationJarTestCase
[01:38:42][org.wildfly:wildfly-ts-integ-basic] Tests run: 7, Failures: 
0, Errors: 0, Skipped: 0, Time elapsed: 1.111 sec - in 
org.jboss.as.test.integration.jca.moduledeployment.MultiActivationJarTestCase
[01:38:42][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.moduledeployment.MultiObjectActivationFlatTestCase
[01:38:43][org.wildfly:wildfly-ts-integ-basic] Tests run: 5, Failures: 
0, Errors: 0, Skipped: 0, Time elapsed: 1.694 sec - in 
org.jboss.as.test.integration.jca.moduledeployment.MultiObjectActivationFlatTestCase
[01:38:43][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.moduledeployment.MultiObjectActivationJarTestCase
[01:38:45][org.wildfly:wildfly-ts-integ-basic] Tests run: 5, Failures: 
0, Errors: 0, Skipped: 0, Time elapsed: 1.24 sec - in 
org.jboss.as.test.integration.jca.moduledeployment.MultiObjectActivationJarTestCase
[01:38:45][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.moduledeployment.PartialObjectActivationFlatTestCase
[02:03:26][org.wildfly:wildfly-ts-integ-basic]
[02:03:26][org.wildfly:wildfly-ts-integ-basic] Results :
[02:03:26][org.wildfly:wildfly-ts-integ-basic]
[02:03:26][org.wildfly:wildfly-ts-integ-basic] Tests run: 36, Failures: 
0, Errors: 0, Skipped: 0
[02:03:26][org.wildfly:wildfly-ts-integ-basic]
[02:03:26][org.wildfly:wildfly-ts-integ-basic] [ERROR] There was a 
timeout or other error in the fork



_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: Timeout errors in JCA bits in testsuite

Stuart Douglas
The whole point of these builds is that it first builds a snapshot of core, then builds full using this snapshot. This verfies that changes in core have not broken anything in full.

Stuart

On Thu, 28 Jan 2016 at 19:58 Carlo de Wolf <[hidden email]> wrote:
There should be no SNAPSHOT dependencies in any CI build. While it does build core beforehand, it might get overwritten by another CI run.
[org.wildfly.core:wildfly-core-parent] [INFO] Installing /opt/buildAgent/work/db872761b443af46/core/pom.xml to /store/repository/org/wildfly/core/wildfly-core-parent/2.0.8.Final-SNAPSHOT/wildfly-core-parent-2.0.8.Final-SNAPSHOT.pom

Would it be possible to use timed snapshots instead?


Carlo


On 01/27/2016 11:55 PM, Brian Stansberry wrote:
In the last day I've seen 3 different CI runs fail due to various JCA 
related tests in testsuite/basic not completing. Does anyone have any 
idea what might be causing this?

The ones I noticed were all PR tests of changes in core. It's hard to 
imagine the PRs themselves were relevant. They do test a snapshot of 
core though, so it's possible some change in core is relevant, in 
addition to the simpler scenario of some issue in full.

1) Just now:

http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildTypeId=WildFlyCore_PullRequest_WildFlyCoreFullIntegration&buildId=87619

[22:05:58][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.moduledeployment.BasicFlatTestCase
[22:06:00][org.wildfly:wildfly-ts-integ-basic] Tests run: 4, Failures: 
0, Errors: 0, Skipped: 0, Time elapsed: 2.084 sec - in 
org.jboss.as.test.integration.jca.moduledeployment.BasicFlatTestCase
[22:06:00][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.moduledeployment.BasicJarTestCase
[22:06:02][org.wildfly:wildfly-ts-integ-basic] Tests run: 4, Failures: 
0, Errors: 0, Skipped: 0, Time elapsed: 1.598 sec - in 
org.jboss.as.test.integration.jca.moduledeployment.BasicJarTestCase
[22:06:02][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.moduledeployment.InflowFlatTestCase
[22:30:48][org.wildfly:wildfly-ts-integ-basic]
[22:30:48][org.wildfly:wildfly-ts-integ-basic] Results :
[22:30:48][org.wildfly:wildfly-ts-integ-basic]
[22:30:48][org.wildfly:wildfly-ts-integ-basic] Tests run: 8, Failures: 
0, Errors: 0, Skipped: 0
[22:30:48][org.wildfly:wildfly-ts-integ-basic]
[22:30:48][org.wildfly:wildfly-ts-integ-basic] [ERROR] There was a 
timeout or other error in the fork

2) Yesterday:

http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=87585&tab=buildResultsDiv&buildTypeId=WF_WildFlyCoreIntegrationExperiments

[14:48:42][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.beanvalidation.PositiveValidationTestCase
[14:48:43][org.wildfly:wildfly-ts-integ-basic] Tests run: 3, Failures: 
0, Errors: 0, Skipped: 0, Time elapsed: 0.669 sec - in 
org.jboss.as.test.integration.jca.beanvalidation.PositiveValidationTestCase
[14:48:43][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.capacitypolicies.DatasourceCapacityPoliciesTestCase
[14:48:44][org.wildfly:wildfly-ts-integ-basic] Tests run: 1, Failures: 
0, Errors: 0, Skipped: 0, Time elapsed: 0.98 sec - in 
org.jboss.as.test.integration.jca.capacitypolicies.DatasourceCapacityPoliciesTestCase
[14:48:44][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.capacitypolicies.ResourceAdapterCapacityPoliciesTestCase
[14:48:44][org.wildfly:wildfly-ts-integ-basic] Tests run: 1, Failures: 
0, Errors: 0, Skipped: 0, Time elapsed: 0.766 sec - in 
org.jboss.as.test.integration.jca.capacitypolicies.ResourceAdapterCapacityPoliciesTestCase
[14:48:44][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.capacitypolicies.XADatasourceCapacityPoliciesTestCase
[14:48:45][org.wildfly:wildfly-ts-integ-basic] Tests run: 1, Failures: 
0, Errors: 0, Skipped: 0, Time elapsed: 0.718 sec - in 
org.jboss.as.test.integration.jca.capacitypolicies.XADatasourceCapacityPoliciesTestCase
[14:48:45][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.datasource.DatasourceEnableAttributeTestCase
[14:48:51][org.wildfly:wildfly-ts-integ-basic] Tests run: 6, Failures: 
0, Errors: 0, Skipped: 0, Time elapsed: 5.881 sec - in 
org.jboss.as.test.integration.jca.datasource.DatasourceEnableAttributeTestCase
[14:48:51][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.datasource.DatasourceXaEnableAttributeTestCase
[15:07:51][org.wildfly:wildfly-ts-integ-basic]
[15:07:51][org.wildfly:wildfly-ts-integ-basic] Results :
[15:07:51][org.wildfly:wildfly-ts-integ-basic]
[15:07:51][org.wildfly:wildfly-ts-integ-basic] Tests run: 761, Failures: 
0, Errors: 0, Skipped: 12
[15:07:51][org.wildfly:wildfly-ts-integ-basic]
[15:07:51][org.wildfly:wildfly-ts-integ-basic] [ERROR] There was a 
timeout or other error in the fork

3) Yesterday:

http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=87425&tab=buildResultsDiv&buildTypeId=WF_WildFlyCoreIntegrationExperiments

[01:38:34][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.moduledeployment.BasicFlatTestCase
[01:38:36][org.wildfly:wildfly-ts-integ-basic] Tests run: 4, Failures: 
0, Errors: 0, Skipped: 0, Time elapsed: 1.583 sec - in 
org.jboss.as.test.integration.jca.moduledeployment.BasicFlatTestCase
[01:38:36][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.moduledeployment.BasicJarTestCase
[01:38:37][org.wildfly:wildfly-ts-integ-basic] Tests run: 4, Failures: 
0, Errors: 0, Skipped: 0, Time elapsed: 1.215 sec - in 
org.jboss.as.test.integration.jca.moduledeployment.BasicJarTestCase
[01:38:37][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.moduledeployment.InflowFlatTestCase
[01:38:38][org.wildfly:wildfly-ts-integ-basic] Tests run: 2, Failures: 
0, Errors: 0, Skipped: 0, Time elapsed: 1.23 sec - in 
org.jboss.as.test.integration.jca.moduledeployment.InflowFlatTestCase
[01:38:38][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.moduledeployment.InflowJarTestCase
[01:38:40][org.wildfly:wildfly-ts-integ-basic] Tests run: 2, Failures: 
0, Errors: 0, Skipped: 0, Time elapsed: 1.086 sec - in 
org.jboss.as.test.integration.jca.moduledeployment.InflowJarTestCase
[01:38:40][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.moduledeployment.MultiActivationFlatTestCase
[01:38:41][org.wildfly:wildfly-ts-integ-basic] Tests run: 7, Failures: 
0, Errors: 0, Skipped: 0, Time elapsed: 1.165 sec - in 
org.jboss.as.test.integration.jca.moduledeployment.MultiActivationFlatTestCase
[01:38:41][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.moduledeployment.MultiActivationJarTestCase
[01:38:42][org.wildfly:wildfly-ts-integ-basic] Tests run: 7, Failures: 
0, Errors: 0, Skipped: 0, Time elapsed: 1.111 sec - in 
org.jboss.as.test.integration.jca.moduledeployment.MultiActivationJarTestCase
[01:38:42][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.moduledeployment.MultiObjectActivationFlatTestCase
[01:38:43][org.wildfly:wildfly-ts-integ-basic] Tests run: 5, Failures: 
0, Errors: 0, Skipped: 0, Time elapsed: 1.694 sec - in 
org.jboss.as.test.integration.jca.moduledeployment.MultiObjectActivationFlatTestCase
[01:38:43][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.moduledeployment.MultiObjectActivationJarTestCase
[01:38:45][org.wildfly:wildfly-ts-integ-basic] Tests run: 5, Failures: 
0, Errors: 0, Skipped: 0, Time elapsed: 1.24 sec - in 
org.jboss.as.test.integration.jca.moduledeployment.MultiObjectActivationJarTestCase
[01:38:45][org.wildfly:wildfly-ts-integ-basic] Running 
org.jboss.as.test.integration.jca.moduledeployment.PartialObjectActivationFlatTestCase
[02:03:26][org.wildfly:wildfly-ts-integ-basic]
[02:03:26][org.wildfly:wildfly-ts-integ-basic] Results :
[02:03:26][org.wildfly:wildfly-ts-integ-basic]
[02:03:26][org.wildfly:wildfly-ts-integ-basic] Tests run: 36, Failures: 
0, Errors: 0, Skipped: 0
[02:03:26][org.wildfly:wildfly-ts-integ-basic]
[02:03:26][org.wildfly:wildfly-ts-integ-basic] [ERROR] There was a 
timeout or other error in the fork


_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev

_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: Timeout errors in JCA bits in testsuite

Tomaž Cerar-2
In reply to this post by Carlo de Wolf

On Thu, Jan 28, 2016 at 9:58 AM, Carlo de Wolf <[hidden email]> wrote:
There should be no SNAPSHOT dependencies in any CI build. While it does build core beforehand, it might get overwritten by another CI run.
[org.wildfly.core:wildfly-core-parent] [INFO] Installing /opt/buildAgent/work/db872761b443af46/core/pom.xml to /store/repository/org/wildfly/core/wildfly-core-parent/2.0.8.Final-SNAPSHOT/wildfly-core-parent-2.0.8.Final-SNAPSHOT.pom

Would it be possible to use timed snapshots instead?


As Stuart said, whole point of this builds is to have snapshot builds.
Same build agent first builds core (clean install) and than builds full
with -Dversion.wildfly.core=<version of wildfly core previousily built>

snapshot used here are only build agent local, not publish on some outside nexus repository.

--
tomaz


_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: Timeout errors in JCA bits in testsuite

Tomaž Cerar-2
In reply to this post by Eduardo Sant´Ana da Silva

On Thu, Jan 28, 2016 at 3:24 AM, Eduardo Sant´Ana da Silva <[hidden email]> wrote:
Seems that this is related to maven, probably something its taking more time than due.



yes those test hang, so after a certain time CI kills the job.

_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: Timeout errors in JCA bits in testsuite

Eduardo Sant´Ana da Silva
In reply to this post by Tomaž Cerar-2
I faced a similar problem recently. 
About this issue, my doubt is that if there is no nexus repository operation, and the build is done sequentially, first core (installing locally), after that the wildfly entire build, how this timeout is occurring?

Seems that this could be a common problem if the maven is executing in parallel and those intermittent problems can occur due synchronization issues.

To resolve my problem I first resolve the dependencies recently installed on local repository through: mvn dependency:build-classpath

---
eduardo

2016-01-28 9:54 GMT-02:00 Tomaž Cerar <[hidden email]>:

On Thu, Jan 28, 2016 at 9:58 AM, Carlo de Wolf <[hidden email]> wrote:
There should be no SNAPSHOT dependencies in any CI build. While it does build core beforehand, it might get overwritten by another CI run.
[org.wildfly.core:wildfly-core-parent] [INFO] Installing /opt/buildAgent/work/db872761b443af46/core/pom.xml to /store/repository/org/wildfly/core/wildfly-core-parent/2.0.8.Final-SNAPSHOT/wildfly-core-parent-2.0.8.Final-SNAPSHOT.pom

Would it be possible to use timed snapshots instead?


As Stuart said, whole point of this builds is to have snapshot builds.
Same build agent first builds core (clean install) and than builds full
with -Dversion.wildfly.core=<version of wildfly core previousily built>

snapshot used here are only build agent local, not publish on some outside nexus repository.

--
tomaz


_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev



--
__________________________
Eduardo Sant'Ana da Silva - Dr.
Pesquisador / Consultor de TI


_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: Timeout errors in JCA bits in testsuite

jtgreene
Administrator
It happens when a test hangs. So we have to get stack traces of the process when this occurs to even know where to being to look. 

On Jan 28, 2016, at 6:38 AM, Eduardo Sant´Ana da Silva <[hidden email]> wrote:

I faced a similar problem recently. 
About this issue, my doubt is that if there is no nexus repository operation, and the build is done sequentially, first core (installing locally), after that the wildfly entire build, how this timeout is occurring?

Seems that this could be a common problem if the maven is executing in parallel and those intermittent problems can occur due synchronization issues.

To resolve my problem I first resolve the dependencies recently installed on local repository through: mvn dependency:build-classpath

---
eduardo

2016-01-28 9:54 GMT-02:00 Tomaž Cerar <[hidden email]>:

On Thu, Jan 28, 2016 at 9:58 AM, Carlo de Wolf <[hidden email]> wrote:
There should be no SNAPSHOT dependencies in any CI build. While it does build core beforehand, it might get overwritten by another CI run.
[org.wildfly.core:wildfly-core-parent] [INFO] Installing /opt/buildAgent/work/db872761b443af46/core/pom.xml to /store/repository/org/wildfly/core/wildfly-core-parent/2.0.8.Final-SNAPSHOT/wildfly-core-parent-2.0.8.Final-SNAPSHOT.pom

Would it be possible to use timed snapshots instead?


As Stuart said, whole point of this builds is to have snapshot builds.
Same build agent first builds core (clean install) and than builds full
with -Dversion.wildfly.core=<version of wildfly core previousily built>

snapshot used here are only build agent local, not publish on some outside nexus repository.

--
tomaz


_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev



--
__________________________
Eduardo Sant'Ana da Silva - Dr.
Pesquisador / Consultor de TI

_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev

_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: Timeout errors in JCA bits in testsuite

Tomaž Cerar-2
it just hanged again,
this is the thread dump http://fpaste.org/315834/53998306/raw/

On Thu, Jan 28, 2016 at 2:12 PM, Jason T. Greene <[hidden email]> wrote:
It happens when a test hangs. So we have to get stack traces of the process when this occurs to even know where to being to look. 

On Jan 28, 2016, at 6:38 AM, Eduardo Sant´Ana da Silva <[hidden email]> wrote:

I faced a similar problem recently. 
About this issue, my doubt is that if there is no nexus repository operation, and the build is done sequentially, first core (installing locally), after that the wildfly entire build, how this timeout is occurring?

Seems that this could be a common problem if the maven is executing in parallel and those intermittent problems can occur due synchronization issues.

To resolve my problem I first resolve the dependencies recently installed on local repository through: mvn dependency:build-classpath

---
eduardo

2016-01-28 9:54 GMT-02:00 Tomaž Cerar <[hidden email]>:

On Thu, Jan 28, 2016 at 9:58 AM, Carlo de Wolf <[hidden email]> wrote:
There should be no SNAPSHOT dependencies in any CI build. While it does build core beforehand, it might get overwritten by another CI run.
[org.wildfly.core:wildfly-core-parent] [INFO] Installing /opt/buildAgent/work/db872761b443af46/core/pom.xml to /store/repository/org/wildfly/core/wildfly-core-parent/2.0.8.Final-SNAPSHOT/wildfly-core-parent-2.0.8.Final-SNAPSHOT.pom

Would it be possible to use timed snapshots instead?


As Stuart said, whole point of this builds is to have snapshot builds.
Same build agent first builds core (clean install) and than builds full
with -Dversion.wildfly.core=<version of wildfly core previousily built>

snapshot used here are only build agent local, not publish on some outside nexus repository.

--
tomaz


_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev



--
__________________________
Eduardo Sant'Ana da Silva - Dr.
Pesquisador / Consultor de TI

_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev


_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: Timeout errors in JCA bits in testsuite

jtgreene
Administrator
Thats the server VM which seems in normal condition.

Here is the surefire VM that is hanging:



Relevant section is:
  1. "main" #1 prio=5 os_prio=0 tid=0xf6606c00 nid=0x4066 in Object.wait() [0xf6752000]
  2.    java.lang.Thread.State: WAITING (on object monitor)
  3.         at java.lang.Object.wait(Native Method)
  4.         at java.lang.Object.wait(Object.java:502)
  5.         at org.xnio.AbstractIoFuture.await(AbstractIoFuture.java:71)
  6.         - locked <0xe0081818> (a java.lang.Object)
  7.         at org.xnio.AbstractIoFuture.get(AbstractIoFuture.java:167)
  8.         - locked <0xe0081818> (a java.lang.Object)
  9.         at org.jboss.as.protocol.mgmt.FutureManagementChannel.openChannel(FutureManagementChannel.java:154)
  10.         at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.openChannel(ManagementClientChannelStrategy.java:150)
  11.         at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.connectionOpened(FutureManagementChannel.java:223)
  12.         at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:79)
  13.         - locked <0xe007d870> (a org.jboss.as.protocol.ProtocolConnectionManager)
  14.         at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:212)
  15.         at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:146)
  16.         - locked <0xe005a3d0> (a org.jboss.as.controller.client.impl.RemotingModelControllerClient)
  17.         at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:65)
  18.         at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:147)
  19.         at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:122)
  20.         at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263)
  21.         at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168)
  22.         at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147)
  23.         at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75)
  24.         at org.jboss.as.test.shared.ServerReload.waitForLiveServerToReload(ServerReload.java:104)
  25.         at org.jboss.as.test.shared.ServerReload.executeReloadAndWaitForCompletion(ServerReload.java:72)
  26.         at org.jboss.as.test.shared.ServerReload.executeReloadAndWaitForCompletion(ServerReload.java:59)
  27.         at org.jboss.as.test.integration.management.jca.DsMgmtTestBase.reload(DsMgmtTestBase.java:56)
  28.         at org.jboss.as.test.integration.jca.datasource.DatasourceXaEnableAttributeTestCase.createDataSource(DatasourceXaEnableAttributeTestCase.java:59)
  29.         at org.jboss.as.test.integration.jca.datasource.DatasourceEnableAttributeTestBase.enableLater(DatasourceEnableAttributeTestBase.java:79)



On Jan 28, 2016, at 10:26 AM, Tomaž Cerar <[hidden email]> wrote:

it just hanged again,
this is the thread dump http://fpaste.org/315834/53998306/raw/

On Thu, Jan 28, 2016 at 2:12 PM, Jason T. Greene <[hidden email]> wrote:
It happens when a test hangs. So we have to get stack traces of the process when this occurs to even know where to being to look. 

On Jan 28, 2016, at 6:38 AM, Eduardo Sant´Ana da Silva <[hidden email]> wrote:

I faced a similar problem recently. 
About this issue, my doubt is that if there is no nexus repository operation, and the build is done sequentially, first core (installing locally), after that the wildfly entire build, how this timeout is occurring?

Seems that this could be a common problem if the maven is executing in parallel and those intermittent problems can occur due synchronization issues.

To resolve my problem I first resolve the dependencies recently installed on local repository through: mvn dependency:build-classpath

---
eduardo

2016-01-28 9:54 GMT-02:00 Tomaž Cerar <[hidden email]>:

On Thu, Jan 28, 2016 at 9:58 AM, Carlo de Wolf <[hidden email]> wrote:
There should be no SNAPSHOT dependencies in any CI build. While it does build core beforehand, it might get overwritten by another CI run.
[org.wildfly.core:wildfly-core-parent] [INFO] Installing /opt/buildAgent/work/db872761b443af46/core/pom.xml to /store/repository/org/wildfly/core/wildfly-core-parent/2.0.8.Final-SNAPSHOT/wildfly-core-parent-2.0.8.Final-SNAPSHOT.pom

Would it be possible to use timed snapshots instead?


As Stuart said, whole point of this builds is to have snapshot builds.
Same build agent first builds core (clean install) and than builds full
with -Dversion.wildfly.core=<version of wildfly core previousily built>

snapshot used here are only build agent local, not publish on some outside nexus repository.

--
tomaz


_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev



--
__________________________
Eduardo Sant'Ana da Silva - Dr.
Pesquisador / Consultor de TI

_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev


--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat


_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: Timeout errors in JCA bits in testsuite

Carlo de Wolf
In reply to this post by Tomaž Cerar-2
I'm not saying, do not use snapshots. I'm saying do not use SNAPSHOT. :-)

Clearly the path is a shared one, so the build must use timed snapshots or risk interference.

Carlo

On 01/28/2016 12:54 PM, Tomaž Cerar wrote:

On Thu, Jan 28, 2016 at 9:58 AM, Carlo de Wolf <[hidden email]> wrote:
There should be no SNAPSHOT dependencies in any CI build. While it does build core beforehand, it might get overwritten by another CI run.
[org.wildfly.core:wildfly-core-parent] [INFO] Installing /opt/buildAgent/work/db872761b443af46/core/pom.xml to /store/repository/org/wildfly/core/wildfly-core-parent/2.0.8.Final-SNAPSHOT/wildfly-core-parent-2.0.8.Final-SNAPSHOT.pom

Would it be possible to use timed snapshots instead?


As Stuart said, whole point of this builds is to have snapshot builds.
Same build agent first builds core (clean install) and than builds full
with -Dversion.wildfly.core=<version of wildfly core previousily built>

snapshot used here are only build agent local, not publish on some outside nexus repository.

--
tomaz



_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: Timeout errors in JCA bits in testsuite

Darran Lofthouse
Every single PR build we execute risks interference.

Without running every PR again after every merge every single PR is a
race condition hoping to avoid conflicting merges.

On 29/01/16 08:02, Carlo de Wolf wrote:

> I'm not saying, do not use snapshots. I'm saying do not use SNAPSHOT. :-)
>
> Clearly the path is a shared one, so the build must use timed snapshots
> or risk interference.
>
> Carlo
>
> On 01/28/2016 12:54 PM, Tomaž Cerar wrote:
>>
>> On Thu, Jan 28, 2016 at 9:58 AM, Carlo de Wolf <[hidden email]
>> <mailto:[hidden email]>> wrote:
>>
>>     There should be no SNAPSHOT dependencies in any CI build. While it
>>     does build core beforehand, it might get overwritten by another CI
>>     run.
>>     //[org.wildfly.core:wildfly-core-parent] /[INFO] Installing
>>     /opt/buildAgent/work/db872761b443af46/core/pom.xml to
>>     /store/repository/org/wildfly/core/wildfly-core-parent/2.0.8.Final-SNAPSHOT/wildfly-core-parent-2.0.8.Final-SNAPSHOT.pom
>>     /
>>     Would it be possible to use timed snapshots instead?
>>
>>
>>
>> As Stuart said, whole point of this builds is to have snapshot builds.
>> Same build agent first builds core (clean install) and than builds full
>> with -Dversion.wildfly.core=<version of wildfly core previousily built>
>>
>> snapshot used here are only build agent local, not publish on some
>> outside nexus repository.
>>
>> --
>> tomaz
>>
>
>
>
> _______________________________________________
> wildfly-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: Timeout errors in JCA bits in testsuite

kkhan
In reply to this post by Carlo de Wolf
The snapshot is local to the build.
On one machine when a core PR is opened:
1) It builds the core snapshot
2) It runs the main build using the snapshot from 1)

The snapshot is not deployed anywhere, and AFAIK removed from the repository when the next build happens.

> On 29 Jan 2016, at 08:02, Carlo de Wolf <[hidden email]> wrote:
>
> I'm not saying, do not use snapshots. I'm saying do not use SNAPSHOT. :-)
>
> Clearly the path is a shared one, so the build must use timed snapshots or risk interference.
>
> Carlo
>
> On 01/28/2016 12:54 PM, Tomaž Cerar wrote:
>>
>> On Thu, Jan 28, 2016 at 9:58 AM, Carlo de Wolf <[hidden email]> wrote:
>> There should be no SNAPSHOT dependencies in any CI build. While it does build core beforehand, it might get overwritten by another CI run.
>> [org.wildfly.core:wildfly-core-parent] [INFO] Installing /opt/buildAgent/work/db872761b443af46/core/pom.xml to /store/repository/org/wildfly/core/wildfly-core-parent/2.0.8.Final-SNAPSHOT/wildfly-core-parent-2.0.8.Final-SNAPSHOT.pom
>>
>> Would it be possible to use timed snapshots instead?
>>
>>
>> As Stuart said, whole point of this builds is to have snapshot builds.
>> Same build agent first builds core (clean install) and than builds full
>> with -Dversion.wildfly.core=<version of wildfly core previousily built>
>>
>> snapshot used here are only build agent local, not publish on some outside nexus repository.
>>
>> --
>> tomaz
>>
>
> _______________________________________________
> wildfly-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/wildfly-dev


_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev