You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cayenne.apache.org by Apache Hudson Server <hu...@hudson.zones.apache.org> on 2009/12/10 16:05:20 UTC
Build failed in Hudson: Cayenne-trunk » derby,JDK 1.6 (latest) #88
See <http://hudson.zones.apache.org/hudson/job/Cayenne-trunk/./cayenneTestConnection=derby,jdk=JDK%201.6%20(latest)/88/changes>
Changes:
[aadamchik] CAY-1323
minor cleanup
------------------------------------------
[...truncated 66024 lines...]
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ID:1772, 2->ID_CLOB:271, 3->VALUE:100]
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ID:1773, 2->ID_CLOB:265, 3->VALUE:100]
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ID:1774, 2->ID_CLOB:298, 3->VALUE:100]
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ID:1775, 2->ID_CLOB:248, 3->VALUE:100]
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ID:1776, 2->ID_CLOB:296, 3->VALUE:100]
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ID:1777, 2->ID_CLOB:227, 3->VALUE:100]
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ID:1778, 2->ID_CLOB:286, 3->VALUE:100]
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ID:1779, 2->ID_CLOB:222, 3->VALUE:100]
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ID:1780, 2->ID_CLOB:246, 3->VALUE:100]
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ID:1781, 2->ID_CLOB:258, 3->VALUE:100]
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ID:1782, 2->ID_CLOB:229, 3->VALUE:100]
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ID:1783, 2->ID_CLOB:299, 3->VALUE:100]
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ID:1784, 2->ID_CLOB:222, 3->VALUE:100]
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ID:1785, 2->ID_CLOB:243, 3->VALUE:100]
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ID:1786, 2->ID_CLOB:268, 3->VALUE:100]
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ID:1787, 2->ID_CLOB:279, 3->VALUE:100]
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ID:1788, 2->ID_CLOB:224, 3->VALUE:100]
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ID:1789, 2->ID_CLOB:277, 3->VALUE:100]
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ID:1790, 2->ID_CLOB:240, 3->VALUE:100]
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ID:1791, 2->ID_CLOB:271, 3->VALUE:100]
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ID:1792, 2->ID_CLOB:286, 3->VALUE:100]
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ID:1793, 2->ID_CLOB:295, 3->VALUE:100]
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ID:1794, 2->ID_CLOB:297, 3->VALUE:100]
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ID:1795, 2->ID_CLOB:289, 3->VALUE:100]
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ID:1796, 2->ID_CLOB:250, 3->VALUE:100]
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ID:1797, 2->ID_CLOB:265, 3->VALUE:100]
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ID:1798, 2->ID_CLOB:278, 3->VALUE:100]
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ID:1799, 2->ID_CLOB:254, 3->VALUE:100]
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logUpdateCount
INFO: === updated 1600 rows.
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logCommitTransaction
INFO: +++ transaction committed.
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logQueryStart
INFO: --- will run 1 query.
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logBeginTransaction
INFO: --- transaction started.
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logQuery
INFO: SELECT t0.CLOB_TEST_ID, t0.CLOB_COL FROM CLOB_TEST t0 JOIN CLOB_TEST_RELATION t1 ON (t0.CLOB_TEST_ID = t1.ID_CLOB) WHERE t1.VALUE = ? [bind: 1->VALUE:100]
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logSelectCount
INFO: === returned 25 rows. - took 83 ms.
Dec 10, 2009 3:05:10 PM org.apache.cayenne.access.QueryLogger logCommitTransaction
INFO: +++ transaction committed.
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.775 sec
Running org.apache.cayenne.access.DataContextQueryCachingTest
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logQueryStart
INFO: --- will run 2 queries.
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logBeginTransaction
INFO: --- transaction started.
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logQuery
INFO: insert into ARTIST (ARTIST_ID, ARTIST_NAME) values (33001, 'aaa')
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logUpdateCount
INFO: === updated 1 row.
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logQuery
INFO: INSERT INTO PAINTING (PAINTING_ID, PAINTING_TITLE, ARTIST_ID, ESTIMATED_PRICE) VALUES (33001, 'P', 33001, 4000)
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logUpdateCount
INFO: === updated 1 row.
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logCommitTransaction
INFO: +++ transaction committed.
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logQueryStart
INFO: --- will run 1 query.
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logBeginTransaction
INFO: --- transaction started.
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logQuery
INFO: SELECT t0.DATE_OF_BIRTH, t0.ARTIST_ID, t0.ARTIST_NAME FROM ARTIST t0
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logSelectCount
INFO: === returned 1 row. - took 80 ms.
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logCommitTransaction
INFO: +++ transaction committed.
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logQueryStart
INFO: --- will run 1 query.
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logBeginTransaction
INFO: --- transaction started.
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logQuery
INFO: update ARTIST set ARTIST_NAME = 'bbb' where ARTIST_ID = 33001
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logUpdateCount
INFO: === updated 1 row.
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logCommitTransaction
INFO: +++ transaction committed.
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logQueryStart
INFO: --- will run 1 query.
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logBeginTransaction
INFO: --- transaction started.
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logQuery
INFO: SELECT t0.DATE_OF_BIRTH, t0.ARTIST_ID, t0.ARTIST_NAME FROM ARTIST t0
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logSelectCount
INFO: === returned 1 row. - took 0 ms.
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logCommitTransaction
INFO: +++ transaction committed.
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.901 sec
Running org.apache.cayenne.access.NestedDataContextParentPeerEventsTest
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logQueryStart
INFO: --- will run 1 query.
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logBeginTransaction
INFO: --- transaction started.
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logQuery
INFO: INSERT INTO ARTIST (ARTIST_ID, ARTIST_NAME, DATE_OF_BIRTH) VALUES (?, ?, ?)
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ARTIST_ID:256, 2->ARTIST_NAME:'X', 3->DATE_OF_BIRTH:NULL]
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logUpdateCount
INFO: === updated 1 row.
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logCommitTransaction
INFO: +++ transaction committed.
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logQueryStart
INFO: --- will run 1 query.
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logBeginTransaction
INFO: --- transaction started.
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logQuery
INFO: UPDATE ARTIST SET ARTIST_NAME = ? WHERE ARTIST_ID = ?
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ARTIST_NAME:'Y', 2->ARTIST_ID:256]
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logUpdateCount
INFO: === updated 1 row.
Dec 10, 2009 3:05:14 PM org.apache.cayenne.access.QueryLogger logCommitTransaction
INFO: +++ transaction committed.
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logQueryStart
INFO: --- will run 2 queries.
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logBeginTransaction
INFO: --- transaction started.
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logQuery
INFO: INSERT INTO ARTIST (ARTIST_ID, ARTIST_NAME, DATE_OF_BIRTH) VALUES (?, ?, ?)
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ARTIST_ID:257, 2->ARTIST_NAME:'Y', 3->DATE_OF_BIRTH:NULL]
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ARTIST_ID:258, 2->ARTIST_NAME:'X', 3->DATE_OF_BIRTH:NULL]
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logUpdateCount
INFO: === updated 2 rows.
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logQuery
INFO: INSERT INTO PAINTING (ARTIST_ID, ESTIMATED_PRICE, GALLERY_ID, PAINTING_DESCRIPTION, PAINTING_ID, PAINTING_TITLE) VALUES (?, ?, ?, ?, ?, ?)
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ARTIST_ID:258, 2->ESTIMATED_PRICE:NULL, 3->GALLERY_ID:NULL, 4->PAINTING_DESCRIPTION:NULL, 5->PAINTING_ID:256, 6->PAINTING_TITLE:'PPP']
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logUpdateCount
INFO: === updated 1 row.
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logCommitTransaction
INFO: +++ transaction committed.
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logQueryStart
INFO: --- will run 1 query.
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logBeginTransaction
INFO: --- transaction started.
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logQuery
INFO: UPDATE PAINTING SET ARTIST_ID = ? WHERE PAINTING_ID = ?
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ARTIST_ID:257, 2->PAINTING_ID:256]
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logUpdateCount
INFO: === updated 1 row.
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logCommitTransaction
INFO: +++ transaction committed.
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logQueryStart
INFO: --- will run 2 queries.
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logBeginTransaction
INFO: --- transaction started.
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logQuery
INFO: INSERT INTO ARTIST (ARTIST_ID, ARTIST_NAME, DATE_OF_BIRTH) VALUES (?, ?, ?)
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ARTIST_ID:259, 2->ARTIST_NAME:'X', 3->DATE_OF_BIRTH:NULL]
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logUpdateCount
INFO: === updated 1 row.
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logQuery
INFO: INSERT INTO PAINTING (ARTIST_ID, ESTIMATED_PRICE, GALLERY_ID, PAINTING_DESCRIPTION, PAINTING_ID, PAINTING_TITLE) VALUES (?, ?, ?, ?, ?, ?)
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ARTIST_ID:NULL, 2->ESTIMATED_PRICE:NULL, 3->GALLERY_ID:NULL, 4->PAINTING_DESCRIPTION:NULL, 5->PAINTING_ID:257, 6->PAINTING_TITLE:'PY']
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ARTIST_ID:259, 2->ESTIMATED_PRICE:NULL, 3->GALLERY_ID:NULL, 4->PAINTING_DESCRIPTION:NULL, 5->PAINTING_ID:258, 6->PAINTING_TITLE:'PX']
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logUpdateCount
INFO: === updated 2 rows.
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logCommitTransaction
INFO: +++ transaction committed.
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logQueryStart
INFO: --- will run 1 query.
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logBeginTransaction
INFO: --- transaction started.
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logQuery
INFO: UPDATE PAINTING SET ARTIST_ID = ? WHERE PAINTING_ID = ?
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logQueryParameters
INFO: [batch bind: 1->ARTIST_ID:259, 2->PAINTING_ID:257]
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logUpdateCount
INFO: === updated 1 row.
Dec 10, 2009 3:05:15 PM org.apache.cayenne.access.QueryLogger logCommitTransaction
INFO: +++ transaction committed.
Dec 10, 2009 3:05:16 PM org.apache.cayenne.access.QueryLogger logQueryStart
INFO: --- will run 1 query.
Dec 10, 2009 3:05:16 PM org.apache.cayenne.access.QueryLogger logBeginTransaction
INFO: --- transaction started.
Dec 10, 2009 3:05:16 PM org.apache.cayenne.access.QueryLogger logQuery
INFO: SELECT t0.ARTIST_ID, t0.PAINTING_ID, t0.GALLERY_ID, t0.PAINTING_DESCRIPTION, t0.ESTIMATED_PRICE, t0.PAINTING_TITLE FROM PAINTING t0 WHERE t0.ARTIST_ID = ? [bind: 1->ARTIST_ID:259]
Dec 10, 2009 3:05:16 PM org.apache.cayenne.access.QueryLogger logSelectCount
INFO: === returned 2 rows. - took 80 ms.
Dec 10, 2009 3:05:16 PM org.apache.cayenne.access.QueryLogger logCommitTransaction
INFO: +++ transaction committed.
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.535 sec
Running org.apache.cayenne.DataRowTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.18 sec
Running org.apache.cayenne.access.types.EnumTypeTest
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec
Running org.apache.cayenne.access.CustomQueryTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Running org.apache.cayenne.project.validator.DomainValidatorTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Results :
Tests in error:
testDifferentEntity(org.apache.cayenne.access.DataContextEJBQLSubqueryTest)
testExists(org.apache.cayenne.access.DataContextEJBQLSubqueryTest)
Tests run: 2052, Failures: 0, Errors: 2, Skipped: 0
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] There are test failures.
Please refer to /zonestorage/hudson/home/hudson/hudson/jobs/Cayenne-trunk/workspace/cayenneTestConnection/derby/jdk/JDK 1.6 (latest)/trunk/framework/cayenne-jdk1.5-unpublished/target/surefire-reports for the individual test results.
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5 minutes 49 seconds
[INFO] Finished at: Thu Dec 10 15:05:17 UTC 2009
[INFO] Final Memory: 56M/196M
[INFO] ------------------------------------------------------------------------
[locks-and-latches] Releasing all the locks
[locks-and-latches] All the locks released
Hudson build is back to normal: Cayenne-trunk » derby,JDK 1.6 (latest) #93
Posted by Apache Hudson Server <hu...@hudson.zones.apache.org>.
See <http://hudson.zones.apache.org/hudson/job/Cayenne-trunk/./cayenneTestConnection=derby,jdk=JDK%201.6%20(latest)/93/changes>
Re: Hudson unit test runs
Posted by Andrey Razumovsky <ra...@gmail.com>.
In other words, I don't think these tests will *ever* work on derby
2009/12/11 Andrey Razumovsky <ra...@gmail.com>
> We're testing Cayenne, not Derby.. Derby limitations is not our fault..
> ideally we should exclude that per DB, but I'd prefer that until we have
> such mechanism in our test framework, tests stiil run fine
>
> 2009/12/11 Andrus Adamchik <an...@objectstyle.org>
>
>
>> On Dec 11, 2009, at 3:32 AM, Andrey Razumovsky wrote:
>>
>> OK, may I suggest we just slightly change the test, so that it works on
>>> Derby as well. Current problem is that Derby does not allow more than one
>>> column in subquery result.
>>> So if wwe replace
>>> "SELECT a FROM Artist a WHERE EXISTS (SELECT DISTINCT p1 ...) "
>>> with
>>> "SELECT a FROM Artist a WHERE EXISTS (SELECT DISTINCT p1.paintingTitle
>>> ...)
>>> "
>>>
>>> it will work with same sense
>>>
>>
>> Then how do we know that the other syntax variant is broken?
>>
>> We clearly need an exclude list per DB...
>>
>> Andrus
>>
>>
>
>
> --
> Andrey
>
--
Andrey
Re: Hudson unit test runs
Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 12/12/09 1:08 AM, Рябицкий Евгений wrote:
> Is it possible to deploy somwhere Oracle Database Express Edition and run Hudsun Unit test on it? Better if it will be near Hudson builder.... could Apache provide some server for that purposes?
> Of couse I can deploy Oracle server at my home computer but this Hudson test are not going to be stable:)
I'm working toward that goal, but first we need to get the resources in place to be able to run all the databases we need for testing. That requires co-operation from Apache infrastructure people. So, in the first instance I'm just working on all the simple databases which can run in memory or be launched from within java.
Ari
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
RE: Hudson unit test runs
Posted by Рябицкий Евгений <er...@diasoft.ru>.
Is it possible to deploy somwhere Oracle Database Express Edition and run Hudsun Unit test on it? Better if it will be near Hudson builder.... could Apache provide some server for that purposes?
Of couse I can deploy Oracle server at my home computer but this Hudson test are not going to be stable :)
Just thoughts... it's really cool that we are adding new DBs but it's sad that we don't try most popular and serious among them.
In production are usually used Oracle, MS SQL, DB2 and Sybase. My gol is to provide support of this data bases.
Evgeny.
-----Original Message-----
From: Andrus Adamchik [mailto:andrus@objectstyle.org]
Sent: Friday, December 11, 2009 4:00 PM
To: dev@cayenne.apache.org
Subject: Re: Hudson unit test runs
I agree with the general statement (and indeed on many DB's we
suppress certain tests, as the DB simply doesn't provide needed
capability). But I think we need to classify this specific case
differently, since Cayenne can still potentially generate the right
single column SQL in this case.
Andrus
On Dec 11, 2009, at 7:52 AM, Andrey Razumovsky wrote:
> We're testing Cayenne, not Derby.. Derby limitations is not our
> fault..
> ideally we should exclude that per DB, but I'd prefer that until we
> have
> such mechanism in our test framework, tests stiil run fine
>
> 2009/12/11 Andrus Adamchik <an...@objectstyle.org>
>
>>
>> On Dec 11, 2009, at 3:32 AM, Andrey Razumovsky wrote:
>>
>> OK, may I suggest we just slightly change the test, so that it
>> works on
>>> Derby as well. Current problem is that Derby does not allow more
>>> than one
>>> column in subquery result.
>>> So if wwe replace
>>> "SELECT a FROM Artist a WHERE EXISTS (SELECT DISTINCT p1 ...) "
>>> with
>>> "SELECT a FROM Artist a WHERE EXISTS (SELECT DISTINCT
>>> p1.paintingTitle
>>> ...)
>>> "
>>>
>>> it will work with same sense
>>>
>>
>> Then how do we know that the other syntax variant is broken?
>>
>> We clearly need an exclude list per DB...
>>
>> Andrus
>>
>>
>
>
> --
> Andrey
Re: Hudson unit test runs
Posted by Andrus Adamchik <an...@objectstyle.org>.
I agree with the general statement (and indeed on many DB's we
suppress certain tests, as the DB simply doesn't provide needed
capability). But I think we need to classify this specific case
differently, since Cayenne can still potentially generate the right
single column SQL in this case.
Andrus
On Dec 11, 2009, at 7:52 AM, Andrey Razumovsky wrote:
> We're testing Cayenne, not Derby.. Derby limitations is not our
> fault..
> ideally we should exclude that per DB, but I'd prefer that until we
> have
> such mechanism in our test framework, tests stiil run fine
>
> 2009/12/11 Andrus Adamchik <an...@objectstyle.org>
>
>>
>> On Dec 11, 2009, at 3:32 AM, Andrey Razumovsky wrote:
>>
>> OK, may I suggest we just slightly change the test, so that it
>> works on
>>> Derby as well. Current problem is that Derby does not allow more
>>> than one
>>> column in subquery result.
>>> So if wwe replace
>>> "SELECT a FROM Artist a WHERE EXISTS (SELECT DISTINCT p1 ...) "
>>> with
>>> "SELECT a FROM Artist a WHERE EXISTS (SELECT DISTINCT
>>> p1.paintingTitle
>>> ...)
>>> "
>>>
>>> it will work with same sense
>>>
>>
>> Then how do we know that the other syntax variant is broken?
>>
>> We clearly need an exclude list per DB...
>>
>> Andrus
>>
>>
>
>
> --
> Andrey
Re: Hudson unit test runs
Posted by Andrey Razumovsky <ra...@gmail.com>.
We're testing Cayenne, not Derby.. Derby limitations is not our fault..
ideally we should exclude that per DB, but I'd prefer that until we have
such mechanism in our test framework, tests stiil run fine
2009/12/11 Andrus Adamchik <an...@objectstyle.org>
>
> On Dec 11, 2009, at 3:32 AM, Andrey Razumovsky wrote:
>
> OK, may I suggest we just slightly change the test, so that it works on
>> Derby as well. Current problem is that Derby does not allow more than one
>> column in subquery result.
>> So if wwe replace
>> "SELECT a FROM Artist a WHERE EXISTS (SELECT DISTINCT p1 ...) "
>> with
>> "SELECT a FROM Artist a WHERE EXISTS (SELECT DISTINCT p1.paintingTitle
>> ...)
>> "
>>
>> it will work with same sense
>>
>
> Then how do we know that the other syntax variant is broken?
>
> We clearly need an exclude list per DB...
>
> Andrus
>
>
--
Andrey
Re: Hudson unit test runs
Posted by Andrus Adamchik <an...@objectstyle.org>.
On Dec 11, 2009, at 3:32 AM, Andrey Razumovsky wrote:
> OK, may I suggest we just slightly change the test, so that it works
> on
> Derby as well. Current problem is that Derby does not allow more
> than one
> column in subquery result.
> So if wwe replace
> "SELECT a FROM Artist a WHERE EXISTS (SELECT DISTINCT p1 ...) "
> with
> "SELECT a FROM Artist a WHERE EXISTS (SELECT DISTINCT
> p1.paintingTitle ...)
> "
>
> it will work with same sense
Then how do we know that the other syntax variant is broken?
We clearly need an exclude list per DB...
Andrus
Re: Hudson unit test runs
Posted by Andrey Razumovsky <ra...@gmail.com>.
OK, may I suggest we just slightly change the test, so that it works on
Derby as well. Current problem is that Derby does not allow more than one
column in subquery result.
So if wwe replace
"SELECT a FROM Artist a WHERE EXISTS (SELECT DISTINCT p1 ...) "
with
"SELECT a FROM Artist a WHERE EXISTS (SELECT DISTINCT p1.paintingTitle ...)
"
it will work with same sense
2009/12/11 Aristedes Maniatis <ar...@maniatis.org>
> On 11/12/09 5:55 PM, Andrey Razumovsky wrote:
>
>> Well, how about the following situation I faced a number of times: the
>> build
>> is broken and I try to fix it. But I don't succeed.. so how should I know
>> about that? Manually go&check in hudson? Not that handy.
>> Of course, Hudson spamming is much worse. I'd rather we disable Derby
>> builds
>> until those two tests can work.
>>
>
> Each of the tests (combinations of java version and db) will send us email
> separately. So if you break hsqldb then none of the other databases will
> even be tested. And separate emails will be sent. Plus we still get the
> email back that the build was a success.
>
>
> Ari
>
>
> --
>
> -------------------------->
> Aristedes Maniatis
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
>
--
Andrey
Re: Hudson unit test runs
Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 11/12/09 5:55 PM, Andrey Razumovsky wrote:
> Well, how about the following situation I faced a number of times: the build
> is broken and I try to fix it. But I don't succeed.. so how should I know
> about that? Manually go&check in hudson? Not that handy.
> Of course, Hudson spamming is much worse. I'd rather we disable Derby builds
> until those two tests can work.
Each of the tests (combinations of java version and db) will send us email separately. So if you break hsqldb then none of the other databases will even be tested. And separate emails will be sent. Plus we still get the email back that the build was a success.
Ari
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
Re: Hudson unit test runs
Posted by Andrey Razumovsky <ra...@gmail.com>.
Well, how about the following situation I faced a number of times: the build
is broken and I try to fix it. But I don't succeed.. so how should I know
about that? Manually go&check in hudson? Not that handy.
Of course, Hudson spamming is much worse. I'd rather we disable Derby builds
until those two tests can work.
2009/12/11 Aristedes Maniatis <ar...@maniatis.org>
> On 11/12/09 12:55 PM, Andrus Adamchik wrote:
>
>>
>> On Dec 10, 2009, at 6:14 PM, Aristedes Maniatis wrote:
>>
>>>
>>>
>>> How about something really simple like
>>>
>>> if (! System.getProperty("CayenneTestConnection").equals("derby")) {
>>> run test...
>>> }
>>>
>>>
>>> That is, if these test failures are actually for real and SHOULD not
>>> pass on Derby. Otherwise, I'll just configure Hudson to only send
>>> emails when the test failures change from run to run, not when they
>>> remain the same.
>>>
>>
>> I think the later option is better for now. IIRC these should work on
>> Derby, but the right implementation is just too quirky and waiting its
>> time.
>>
>> Andrus
>>
>
>
> OK, I've done that now. We will not get emails after the first broken
> build.
>
> Do we need Jira(s) for the broken tests on Derby? Are they the same issue
> or two different things?
>
>
> Ari Maniatis
>
>
> --
>
> -------------------------->
> Aristedes Maniatis
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
>
--
Andrey
Hudson unit test runs
Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 11/12/09 12:55 PM, Andrus Adamchik wrote:
>
> On Dec 10, 2009, at 6:14 PM, Aristedes Maniatis wrote:
>>
>>
>> How about something really simple like
>>
>> if (! System.getProperty("CayenneTestConnection").equals("derby")) {
>> run test...
>> }
>>
>>
>> That is, if these test failures are actually for real and SHOULD not
>> pass on Derby. Otherwise, I'll just configure Hudson to only send
>> emails when the test failures change from run to run, not when they
>> remain the same.
>
> I think the later option is better for now. IIRC these should work on
> Derby, but the right implementation is just too quirky and waiting its
> time.
>
> Andrus
OK, I've done that now. We will not get emails after the first broken build.
Do we need Jira(s) for the broken tests on Derby? Are they the same issue or two different things?
Ari Maniatis
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
Re: Build failed in Hudson: Cayenne-trunk » derby,JDK 1.6 (latest) #88
Posted by Andrus Adamchik <an...@objectstyle.org>.
On Dec 10, 2009, at 6:14 PM, Aristedes Maniatis wrote:
>
>
> How about something really simple like
>
> if (! System.getProperty("CayenneTestConnection").equals("derby")) {
> run test...
> }
>
>
> That is, if these test failures are actually for real and SHOULD not
> pass on Derby. Otherwise, I'll just configure Hudson to only send
> emails when the test failures change from run to run, not when they
> remain the same.
I think the later option is better for now. IIRC these should work on
Derby, but the right implementation is just too quirky and waiting its
time.
Andrus
Re: Build failed in Hudson: Cayenne-trunk » derby,JDK 1.6 (latest) #88
Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 11/12/09 5:17 AM, Andrus Adamchik wrote:
> These are all known issues with Derby... E.g. from the last release vote
> thread:
>
> On Nov 6, 2009, at 11:22 AM, Ольга Ткачева wrote:
>
>> Derby (2 Tests in error: )
>> -
>> testDifferentEntity(org.apache.cayenne.access.DataContextEJBQLSubqueryTest)
>>
>> - testExists(org.apache.cayenne.access.DataContextEJBQLSubqueryTest)
>
>
> Once we migrate to a better test infrastructure, there should be a way
> to selectively disable tests for certain DBs. For now we have to deal
> with partial failures on some of them.
How about something really simple like
if (! System.getProperty("CayenneTestConnection").equals("derby")) {
run test...
}
That is, if these test failures are actually for real and SHOULD not pass on Derby. Otherwise, I'll just configure Hudson to only send emails when the test failures change from run to run, not when they remain the same.
Ari
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
Re: Build failed in Hudson: Cayenne-trunk » derby,JDK 1.6 (latest) #88
Posted by Andrus Adamchik <an...@objectstyle.org>.
These are all known issues with Derby... E.g. from the last release
vote thread:
On Nov 6, 2009, at 11:22 AM, Ольга Ткачева wrote:
> Derby (2 Tests in error: )
> -
> testDifferentEntity
> (org.apache.cayenne.access.DataContextEJBQLSubqueryTest)
> - testExists(org.apache.cayenne.access.DataContextEJBQLSubqueryTest)
Once we migrate to a better test infrastructure, there should be a way
to selectively disable tests for certain DBs. For now we have to deal
with partial failures on some of them.
Andrus
On Dec 10, 2009, at 12:14 PM, Aristedes Maniatis wrote:
> On 11/12/09 2:05 AM, Apache Hudson Server wrote:
>> Tests in error:
>>
>> testDifferentEntity
>> (org.apache.cayenne.access.DataContextEJBQLSubqueryTest)
>> testExists(org.apache.cayenne.access.DataContextEJBQLSubqueryTest)
>
>
> I've got good news and bad news. The good news is that Hudson is now
> running tests for Derby and H2 as it should. The bad news is that
> Derby doesn't pass.
>
> Are these faults specific to the Hudson server or do we have a
> problem? I haven't got time to dig around any more... I've just
> spent way too long getting Hudson to do what I want and need to go
> to bed now.
>
> Ari
>
> --
>
> -------------------------->
> Aristedes Maniatis
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
>
Re: Build failed in Hudson: Cayenne-trunk » derby,JDK 1.6 (latest) #88
Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 11/12/09 2:05 AM, Apache Hudson Server wrote:
> Tests in error:
> testDifferentEntity(org.apache.cayenne.access.DataContextEJBQLSubqueryTest)
> testExists(org.apache.cayenne.access.DataContextEJBQLSubqueryTest)
I've got good news and bad news. The good news is that Hudson is now running tests for Derby and H2 as it should. The bad news is that Derby doesn't pass.
Are these faults specific to the Hudson server or do we have a problem? I haven't got time to dig around any more... I've just spent way too long getting Hudson to do what I want and need to go to bed now.
Ari
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A