This is the mail archive of the mailing list for the Mauve project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Question about getEncoding method on different platforms


I updated Mauve today and some of the errors where corrected. It seems like the code was not updated for gnu/testlet/java/io/PipedStream/ code available() and for gnu/testlet/java/io/OutputStreamWriter/

 FAIL: OutputStreamWriter(writer, encoding) (number 1)
got ISO8859_3 but expected 8859_3

>  // Now set up our reader
>       PipedInputStream pis = new PipedInputStream();
>       pis.connect(pos);
>       new Thread(pstw).start();
>            harness.check(pis.available() > 0, "available()");

Also, If I could get write access to CVS that would be ok for future updates.

Pat Ellis
SDE Build and Test Team
Phone:      (919) 531-0355   
R2263     Patrick dot Ellis at sas dot com
SAS...  The Power to Know

-----Original Message-----
From: Brian Jones [mailto:cbj at gnu dot org] 
Sent: Wednesday, March 05, 2003 11:37 PM
To: Patrick Ellis
Cc: mauve-discuss at sources dot redhat dot com
Subject: Re: Question about getEncoding method on different platforms

"Patrick Ellis" <Patrick dot Ellis at sas dot com> writes:

> I have testcases that are failing across several platforms because the 
> encoding value that is returned from the different platforms does not 
> match the 8859_1 value that is being expected by the testcase. Example 
> the value of ASCII is returned for Sun and Linux.
> Question: Should the mauve code be changed to reflect the correct 
> values expected for each platform ?

Again check to see if you've updated your Mauve since Mark checked this in... 

Btw, you seem to be using Mauve a lot.  Have you considered whether you need the ability to commit new tests or changes to CVS more directly?  Getting write access to CVS is pretty easy with Mauve.

2003-02-13  Mark Wielaard  <mark at klomp dot org>

        * gnu/testlet/java/io/InputStreamReader/ (test): Just check
        that encoding is non-null when opened and null when closed. Checking
        the actual encoding name is as good as impossible pre 1.4.
        * gnu/testlet/java/io/OutputStreamWriter/ (test):Likewise.

Brian Jones <cbj at gnu dot org>

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]