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
