commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: [continuum] BUILD FAILURE: Commons - Commons DBCP - Try debug build
Date Thu, 14 Jan 2010 14:34:41 GMT
On 14/01/2010, Continuum@vmbuild.apache.org <continuum@apache.org> wrote:
> Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=269640&projectId=22
>
>
>  Build statistics:
>   State: Failed
>   Previous State: Failed
>
>   Started at: Thu 14 Jan 2010 06:05:51 -0800
>   Finished at: Thu 14 Jan 2010 06:07:58 -0800
>   Total time: 2m 7s
>
>   Build Trigger: Schedule
>   Build Number: 149
>   Exit code: 1
>   Building machine hostname: vmbuild.apache.org
>   Operating system : Linux(unknown)
>   Java Home version :
>           java version "1.6.0_06"
>           Java(TM) SE Runtime Environment (build 1.6.0_06-b02)
>           Java HotSpot(TM) Client VM (build 10.0-b22, mixed mode, sharing)
>
>   Builder version :
>           Maven version: 2.0.9
>           Java version: 1.6.0_06
>           OS name: "linux" version: "2.6.24-23-server" arch: "i386" Family: "unix"
>
>  ****************************************************************************
>  SCM Changes:
>  ****************************************************************************
>
> Changed: sebb @ Thu 14 Jan 2010 05:24:47 -0800
>  Comment: Use hash of innermostDelegate to show connection reuse
>  Files changed:
>   /commons/proper/dbcp/trunk/src/test/org/apache/commons/dbcp/TestConnectionPool.java
( 899189 )
>
>
>  ****************************************************************************
>  Dependencies Changes:
>  ****************************************************************************
>  No dependencies changed
>
>
>  ****************************************************************************
>  Build Definition:
>  ****************************************************************************
>  POM filename: pom.xml
>  Goals: clean test
>  Arguments: --batch-mode -DargLine="-DTestConnectionPool.display.thread.details=true"
>  Build Fresh: false
>  Always Build: true
>  Default Build Definition: true
>  Schedule: COMMONS_SCHEDULE
>  Profile Name: JDK 6
>  Description: Try debug build
>
>  ****************************************************************************
>  Test Summary:
>  ****************************************************************************
>  Tests: 445
>  Failures: 2
>  Errors: 0
>  Success Rate: 99
>
> Total time: 48.891
>
>
>  ****************************************************************************
>  Test Failures:
>  ****************************************************************************
>
>  TestSharedPoolDataSource
>     testMultipleThreads2 :
>   junit.framework.AssertionFailedError
>   junit.framework.AssertionFailedError: WARNING: Expected half the threads to fail expected:<10>
but was:<9>
>         at junit.framework.Assert.fail(Assert.java:47)
>         at junit.framework.Assert.failNotEquals(Assert.java:280)
>         at junit.framework.Assert.assertEquals(Assert.java:64)
>         at junit.framework.Assert.assertEquals(Assert.java:198)
>         at org.apache.commons.dbcp.TestConnectionPool.multipleThreads(TestConnectionPool.java:802)
>         at org.apache.commons.dbcp.datasources.TestSharedPoolDataSource.testMultipleThreads2(TestSharedPoolDataSource.java:375)
>

This was probably due to a thread finishing early:

Pre: 1039. Post: 1441. Hash: 25559096.
Pre: 1063. Post: 1549. Hash: 24745276.
Pre: 1063. Post: 1549. Hash: 18945918.
Pre: 1074. Post: 1549. Hash: 20089978.
Pre: 1087. Post: 1549. Hash: 12829461.
Pre: 1137. Post: 1548. Hash: 1673653.
Pre: 1192. Post: 1548. Hash: 19673895.
Pre: 1248. Post: 1548. Hash: 17777129.
Pre: 1273. Post: 1581. Hash: 15734641.
Pre: 1274. Post: 1581. Hash: 11511434.
Pre: 1288. Post: -. Hash: 0. Startup:
Pre: 1301. Post: -. Hash: 0. Startup:
Pre: 1339. Post: 1741. Hash: 25559096.

The first thread finishes at 1441 and the last thread shown above
starts waiting for the connection at around the same time (1339), and
gets the same connection.

The time overlap here is reasonable, as the synch. section of code
must be slightly shorther than the time we can measure in the test
case.

Need to wait for some more convincing test output.

>
>   TestPerUserPoolDataSource
>
>     testMultipleThreads2 :
>   junit.framework.AssertionFailedError
>   junit.framework.AssertionFailedError: WARNING: Expected half the threads to fail expected:<10>
but was:<3>
>         at junit.framework.Assert.fail(Assert.java:47)
>         at junit.framework.Assert.failNotEquals(Assert.java:280)
>         at junit.framework.Assert.assertEquals(Assert.java:64)
>         at junit.framework.Assert.assertEquals(Assert.java:198)
>         at org.apache.commons.dbcp.TestConnectionPool.multipleThreads(TestConnectionPool.java:802)
>
>         at org.apache.commons.dbcp.datasources.TestPerUserPoolDataSource.testMultipleThreads2(TestPerUserPoolDataSource.java:385)
>
>

That one was definitely due to a thread finishing early.

>
>
>  ---------------------------------------------------------------------
>
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>  For additional commands, e-mail: dev-help@commons.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message