Hi Kevin,
No immediate ideas on this, but if you end up disabling the tests then
could you also raise a ticket so that we don't lose this issue?
In terms of debugging, it's presumably some sort of environmental
thing. Or, (and this is a bit of a long shot) I wonder if it's when the
tests are run... around about midnight?
At any rate, if you put some System.out.println's in, then these will
appear in the console output of the jobs. A bit low tech, but might
give some clues.
You might also want to see if you have access to run the job... you
might need an account on hudson.apache.org. I can't quite remember
where I got mine - I think that Nour helped out, so perhaps he might
chime in?
Cheers
Dan
On 09/02/2011 08:02, Kevin Meyer - KMZ wrote:
Hmm.. some help here, please..
The test passes on my machine, and used to pass before. I would
guess that it is the way that DATE is handled on the Hudson machine.
Hmm.. some further thinking is required.. I am using the same version
of HSQLDB (1.8.0) as Hudson machine.. I'll temporarily disable the
date tests.
Regards,
Kevin
On 9 Feb 2011 at 0:42, Apache Hudson Server wrote:
See<https://hudson.apache.org/hudson/job/isis-trunk-ubuntu/org.apache.isis.alternatives.objectstore$sql-tests-common/82/>
Caused by:
Failed
org.apache.isis.alternatives.objectstore.sql.HsqlTest.testDate
Failing for the past 2 builds (Since Unstable#81 )
Took 3 ms.
Error Message
2010-3-5 is not equal to 2010-3-4
Stacktrace
junit.framework.AssertionFailedError: 2010-3-5 is not equal to 2010-3-4
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at
org.apache.isis.alternatives.objectstore.sql.common.SqlIntegrationTestCommon.testDate(SqlIntegrationTestCommon.java:308)
