harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Geir Magnusson Jr <g...@pobox.com>
Subject Re: Bug for bug compatibility (was Re: [jira] Closed: (HARMONY-311) java.io.FileInputStream.skip(long n) returns incorrect value)
Date Tue, 11 Apr 2006 01:01:49 GMT


George Harley wrote:
> Hi,
> 
> Would it be possible to have a resolution option of "Matching RI Bug" 
> (or similar) when closing a JIRA issue with the resolution that we are 
> matching an apparent RI bug ? Hopefully, it should make it easier to 
> find all such issues in the future.

Well.... one bug in JIRA's design is that resolutions are global.  So we 
could add it, but then every other project at Apache gets that on the 
resolution pick-list.

The other problem I see is that it's orthogonal information, of sorts... 
  I mean, what if someone was reporting a bug, and we decide to call it 
'matching'? or if you make a change to align w/ the RI, that's 
'matching' too, but the diff is that one is "won't fix" and one is "fixed".

How about re-visiting the JIRA category idea - we change the current 
"Non-bug differences from RI" category to also include "Matching Bugs" 
(which is "difference from spec" among other things..."

So maybe "differences from RI or spec" category?  or "RI and spec diffs 
and bugs"?

geir

> 
> Best regards,
> George
> 
> 
> George Harley (JIRA) wrote:
>>      [ http://issues.apache.org/jira/browse/HARMONY-311?page=all ]
>>      George Harley closed HARMONY-311:
>> ---------------------------------
>>
>>     Resolution: Won't Fix
>>
>> This is a case of Harmony matching the behaviour of an apparent RI bug.
>>
>>  
>>> java.io.FileInputStream.skip(long n) returns incorrect value
>>> ------------------------------------------------------------
>>>
>>>          Key: HARMONY-311
>>>          URL: http://issues.apache.org/jira/browse/HARMONY-311
>>>      Project: Harmony
>>>         Type: Bug
>>>     
>>
>>  
>>>   Components: Classlib
>>>     Reporter: nikolay
>>>     Assignee: George Harley
>>>  Attachments: patch.txt
>>>
>>> According to  J2SE 1.4.2, 1.5.0 specifications for 
>>> java.io.FileInputStream.skip(long n)
>>> the method should return the actual number of bytes skipped.
>>> The test listed below shows that the method returns incorrect value 
>>> if parameter > number of bytes in file.
>>> import java.io.FileInputStream; import java.io.IOException; import 
>>> java.io.File; public class Test{     public static void main(String[] 
>>> args) {         FileInputStream toRet = null;         try { 
>>>             File file = new File("FileInStream.tmp");             
>>> file.createNewFile();             toRet = new FileInputStream(file); 
>>>             System.out.println("skipped = " + toRet.skip(100)); 
>>>         } catch (IOException e) {             e.printStackTrace(); 
>>>         }     }    } Output RI: java.exe -showversion Test java 
>>> version "1.4.2_04"
>>> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
>>> BEA WebLogic JRockit(TM) 1.4.2_04 JVM  (build 
>>> ari-31788-20040616-1132-win-ia32,
>>> Native Threads, GC strategy: parallel)
>>> skipped = 0
>>> Output harmony:
>>> java -showversion Test java version 1.4.2 (subset)
>>> (c) Copyright 1991, 2005 The Apache Software Foundation or its 
>>> licensors, as applicable.
>>> skipped = 100     
>>
>>   
> 
> 
> ---------------------------------------------------------------------
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
> For additional commands, e-mail: harmony-dev-help@incubator.apache.org
> 
> 

---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org


Mime
View raw message