Hi Dushshantha,
The corrupted strings in ComplexLists is a separate problem that Carsten
and I are working on. It also affects AxisBench. Of course if you see the
fix to it, please let us know :-)
Mark
Mark Whitlock
IBM
----- Forwarded by Mark Whitlock/UK/IBM on 07/07/2005 09:47 -----
"Dushshantha
Chandradasa"
<[EMAIL PROTECTED] To
tusa.com> "Apache AXIS C Developers List"
<[email protected]>
07/07/2005 08:48 cc
Subject
Please respond to RE: unitTest in build process
"Apache AXIS C
Developers List"
Hi John,
I tested the new target on Windows and it is working fine for up to
certain level and hangs with the following messages on the screen.
[exec] ResponseSender: Sent response To Client
[exec] at
sun.nio.cs.StreamDecoder.read(StreamDecoder.java:183)
[exec] at
java.io.InputStreamReader.read(InputStreamReader.java:167)
[exec] at
java.io.BufferedReader.read1(BufferedReader.java:185)
[exec] at
java.io.BufferedReader.read(BufferedReader.java:261)
[exec] at java.io.Reader.read(Reader.java:122)
[exec] at org.apache.test.MockServerThread.run(Unknown
Source)
[exec] at java.lang.Thread.run(Thread.java:595)
[exec] MockServerThread#run(): exit
[stopwatch] [UnitTest_XSD_nonPositiveInteger.timer: 0.218 sec]
[echo] UnitTest_XSD_nonPositiveInteger - Execution Time - 0.218
sec
stopMonitor:
[java] StopTCPMonitor#stopMonitor(): Sending stop message to
monitor
[java] Mockserver#run(): Got a new client request
[java] MockServerThread(): entry
[java] MockServerThread#run():About to wait for stop msg
I ran the build target again without changing anything and I found
that I is working smoothly up to the end (is this a memory issue??)
We’ll test this on Linux platform today and let you know the results.
I noticed that some of the tests are failing specially ComplexLists
as it returns garbage. The problem should be with the Deserialization
of the client side.
The .out file of this test is as follows
request successful
7
x
Í`ÐÐÒàÓ
request successful
7
x
Í`ÐÐÒàÓ
ale->errortext is NULL
ale->errorcode is NULL
request successful
7
x
Í`ÐÐÒàÓ
---------------------- TEST COMPLETE -----------------------------
I think that some recent changes in the deserialization lead the test
to this error. Currently I’m working on to add more unit tests to the
system. Yesterday I could not look in to that because I found a build
breakage on Linux and AIX as a result of my changes on Exception
model so I fixed it and tested.
Thanks,
Dushshantha
From: John Hawkins [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 06, 2005 1:37 AM
To: [email protected]
Subject: unitTest in build process
Hi folks,
I've created a new target in build.xml called buildAndRunUnitTests. It
works OK for me but before I make it the default target can someone else
please try it out? Just call the build.xml file as you would normally but
call the target buildAndRunUnitTests. Your cmd line should look something
like ->
ant <your usual build.xml -D options if you use any> <-file build.xml>
buildAndRunUnitTests
When we're happy that it works with everyone's environment I'll make it the
default target.
I'd also like to make it stop the build if it fails to run the unit tests
correctly (if everyone agrees) - I don't see the point in having the unit
tests if they can fail and not stop the build.
cheers for now,
John.
