Hi Brian,
I ran this about 9PST and again at 4.53PST and received:
testConversionsFromDay
(org.apache.tuscany.sdo.test.DateConversionTestCase) Time elapsed:
0.01 sec <<< FAILURE!
[ stacktrace ]
-----------------------------------------------------------
junit.framework.AssertionFailedError: The expected value did not
result when calling toDay after initializing with toDay.
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at org.apache.tuscany.sdo.test.DateConversionTestCase
$Test.executeConversion(DateConversionTestCase.java:167)
at org.apache.tuscany.sdo.test.DateConversionTestCase
$Test.attemptConversion(DateConversionTestCase.java:148)
at
org.apache.tuscany.sdo.test.DateConversionTestCase.testConversionsFromDa
y(DateConversionTestCase.java:200)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
I'm on OS X and JDK:
java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-112)
Java HotSpot(TM) Client VM (build 1.5.0_06-64, mixed mode, sharing)
This isn't blocking anything I'm working on but I'm happy to help
diagnose the problem.
Jim
On Aug 25, 2006, at 11:55 AM, Brian Murray wrote:
Hello Jim,
I attempted this on a variety of time/timezone environments and
thought I
had addressed all the possibilities in terms of TimeZones, daylight
savings
time, northern and southern hemispheres, etc. Can you tell me what
TimeZone
you are in and about what time you ran the test with failure?
On 8/25/06, Jim Marino <[EMAIL PROTECTED]> wrote:
I just synced SDO and am getting the following when building from /
java:
junit.framework.AssertionFailedError: The expected value did not
result when calling toDay after initializing with toDay.
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at org.apache.tuscany.sdo.test.DateConversionTestCase
$Test.executeConversion(DateConversionTestCase.java:167)
at org.apache.tuscany.sdo.test.DateConversionTestCase
$Test.attemptConversion(DateConversionTestCase.java:148)
at
org.apache.tuscany.sdo.test.DateConversionTestCase.testConversionsFro
mDa
y(DateConversionTestCase.java:200)
I would be surprised if this is from any of the changes to SCA.
Jim
On Aug 25, 2006, at 9:08 AM, Jim Marino wrote:
> Hi Ignacio,
>
> The build runs fine for me. Did you try mvn clean first? Can you
> send a stacktrace if it persists?
>
> Jim
>
> On Aug 25, 2006, at 7:00 AM, Ignacio Silva-Lepe wrote:
>
>> The latest update, that updates a lot of the core/implementation/
>> processors, seems to be breaking a lot if not all of the sca
>> samples. The way I see this is by doing a mvn clean and mvn -e
>> from the top, which breaks while running the tests for the SDO
>> impl, so then I go to sca/core and do mvn -e and then go to
>> samples/sca and do mvn -e. This is where I see various exceptions
>> from processors such as ServiceProcessor and
>> HeuristicPojoProcessor, including NPE, from samples that used to
>> run, such as supply chain and samplecallback.
>> Any ideas?
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
