Seems that this is related to maven, probably something its taking more time than due. https://maven.apache.org/surefire/maven-failsafe-plugin/examples/shutdown...

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=WildFlyCor... [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=... [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=... [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 wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev

On Thu, Jan 28, 2016 at 9:58 AM, Carlo de Wolf <cdewolf(a)redhat.com&gt; 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 wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev

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 < eduardo.santanadasilva(a)gmail.com&gt; 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 <tomaz.cerar(a)gmail.com&gt;: > > On Thu, Jan 28, 2016 at 9:58 AM, Carlo de Wolf <cdewolf(a)redhat.com&gt; > 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 > wildfly-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev > -- __________________________ Eduardo Sant'Ana da Silva - Dr. Pesquisador / Consultor de TI _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev

On Thu, Jan 28, 2016 at 9:58 AM, Carlo de Wolf <cdewolf(a)redhat.com <mailto:cdewolf@redhat.com>> 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

On 29 Jan 2016, at 08:02, Carlo de Wolf <cdewolf(a)redhat.com&gt; 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 <cdewolf(a)redhat.com&gt; 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 wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev