Just added -e flag to trunk and 3.0 builds so that Maven errors are
more verbose, and re-ran the trunk build manually.
So yeah, I can confirm that "successful" builds are all running
against HSQLDB (no matter whether it says Derby or H2). Can we lock
all builds to specific machines, and place connection.properties on
each one of those?
(BTW, I don't have SSH on minerva.apache.org or vesta.apache.org, I
asked Tim to set me up).
Also HSQLDB profile is officially named "internal_embedded_datasource"
in Cayenne, so I guess we should use this as a Hudson name as well
name to match what we have in the POM. (or rename it in Cayenne)
Andrus
On Jan 4, 2010, at 12:53 PM, Aristedes Maniatis wrote:
> On 4/01/10 9:43 PM, Apache Hudson Server wrote:
>> Failed tests:
>> warning(junit.framework.TestSuite$1)
>> testLoad(org.apache.cayenne.access.DbLoaderTest)
>>
>> Tests in error:
>> testInsert(org.apache.cayenne.access.EmbeddingTest)
>> testSelect(org.apache.cayenne.access.EmbeddingTest)
>>
>> testUpdateEmbeddedProperties(org.apache.cayenne.access.EmbeddingTest)
>> testUpdateEmbedded(org.apache.cayenne.access.EmbeddingTest)
>
>
> I'm thinking that this test is bouncing between success and failed
> because the job was previously running on different Hudson clients.
> I've now set it to only run on the Hudson master which has the
> connection dictionary installed.
>
> So the above errors are probably real.
>
>
> Ari
>
> --
>
> -------------------------->
> Aristedes Maniatis
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
>
This archive was generated by hypermail 2.0.0 : Mon Jan 04 2010 - 10:27:43 EST