+1
I guess that you are not using the Ant test framework as that performs an
EOL/newline conversion of both the output file and the expected output file
so the comparison is performed platform independently. In Ant the fixcrlf
task does this for you. On linux you can use dos2unix to perform a similar
task.
Regards,
Andrew Perry
IBM Web Services Client for C/C++
[EMAIL PROTECTED]
Mail Point 127
IBM UK Laboratories. Hursley Park, Winchester, Hants. SO21 2JN
Tel. Internal 249828 External + 44 (0)1962 819828
Fax. + 44(0)1962 818080
Samisa Abeysinghe
<samisa.abeysingh
[EMAIL PROTECTED]>
To
Apache AXIS C Developers List
01/04/2005 12:11 <[email protected]>
cc
Please respond to Subject
"Apache AXIS C Re: 1.5 Release and codefreeze
Developers List"
The garbage problem is solved now.
With the tests we have done so far, out of the 126 tests, 61 is
directly passing.
Another 40 + are running but shows as failed due to differences in the
expected output file content and actual file output content (This
happens because at times there are some newline handling differernaces
in Java services and C++ services)
However, we can conside them as passing because they give out valid output.
We hope that we would be able to fix some of the failing few on Monday.
As we have considerable stability, I would like to propose an early
Monday code freeze.
Thanks,
Samisa...
On Mar 30, 2005 9:56 PM, Samisa Abeysinghe <[EMAIL PROTECTED]> wrote:
> I have been able to fix the garbage return problem for server side
> generated code.
>
> We are seeing some server side problems in case of IHeadeBlock tests and
> IAttribute tests. This we hope will be able to solve soon.
>
> We are in good shape to freeze the code now - Sanjaya, I think we should
> be tagging the CVS for code freeze by EOD today or tomorrow morning.
>
> Thoughts please.
>
> Thanks,
> Samisa...
>
> On Wed, 2005-03-30 at 08:10, John Hawkins wrote:
> > Please be aware that we are not running the client tests for the next
> > few days so cannot help on whether the client is good or not on all
> > platforms.
> >
> >
> >
> >
> > "Samisa Abeysinghe"
> > <[EMAIL PROTECTED]>
> >
> > 30/03/2005 04:20
> > Please respond to
> > "Apache AXIS C Developers List"
> > To
> > "Apache AXIS C
> > Developers List"
> > <[email protected]>
> > cc
> >
> > Subject
> > RE: 1.5 Release
> > and codefreeze
> >
> >
> >
> >
> > We have one critical issue on the server side, where the server
> > returns garbage at some instances. I am looking into this.
> >
> > Other than that, tests with C++ server side are looking good.
> >
> >
> >
> > Thanks,
> >
> > Samisaâ
> >
> >
> >
> > -----Original Message-----
> > From: John Hawkins [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, March 29, 2005 9:58 PM
> > To: Apache AXIS C Developers List
> > Subject: Re: 1.5 Release and codefreeze
> >
> >
> >
> >
> > Hi Sanjaya,
> >
> > I was just wondering this myself today !
> >
> > Code-freeze should be when we get a build that passes 100% of the test
> > cases? We've currently got a few failing that I believe samisa was
> > looking at?
> >
> > What will happen between codefreeze and release date will dictate the
> > time frame won't it?
> >
> >
> >
> >
> >
> >
> >
> > "sanjaya singharage"
> > <[EMAIL PROTECTED]>
> >
> > 29/03/2005 13:59
> >
> >
> > Please respond to
> > "Apache AXIS C Developers List"
> >
> > To
> > "Apache AXIS C
> > Developers List"
> > <[email protected]>
> > cc
> >
> > Subject
> > 1.5 Release and
> > codefreeze
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Can we decide on a date for codefreeze for the 1.5 final release?
> >
> > And a release date as well.
> >
> > Also if there are outstanding issues could we list them out so that we
> > can
> > systematically attend to them?
> >
> > sanjaya.
> >
> --
> Samisa Abeysinghe <[EMAIL PROTECTED]>
> Virtusa Corporation
>
