octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 3.4 and bug reports


From: Tatsuro MATSUOKA
Subject: Re: 3.4 and bug reports
Date: Thu, 10 Feb 2011 13:27:02 +0900 (JST)

Hello

--- "John W. Eaton"  wrote:

> On  8-Feb-2011, Rik wrote:
> 
> | How do we want to handle the many reports on the bug tracker which deal
> | with older versions of Octave?  Many distros, like Fedora, simply go
> | through and close down the old reports and ask users to re-submit if the
> | problem persists.  This is mildly rude, but also a big time-saver because a
> | lot of these problems were with building intermediate development versions
> | of Octave.  These will have been fixed by the 3.4.0 release, or they would
> | need to be updated anyways to make it clear that something is still wrong.
> 
> I don't think it makes sense to close everything just because there is
> a new release.  But it would be helpful to go back and check old
> reports again.  If they appear to be fixed with the new release, then
> I'd say it's OK to close them.  I'm not sure what to do about those
> that can't be duplicated or for which we can't get responses to
> questions we ask to clarify our understanding of the problem (usually
> that means we are having trouble with duplicating the problem).  If we
> just close them, then we may be ignoring real problems, but that
> happen on systems we don't have, or that happen for specific sets of
> dependencies, compiler and library versions, etc., that are not clear
> from the report.

Sorry off topic wrying but some relation might exist. 

I have finished to build octave-3.4.0 on MinGW.
I have carried out the fntests. The list of the results are

Integrated test scripts:

  d:\usr\Tatsu\mingwhome\octaves\octavesrc\octave-3.4.0\src\data.cc  PASS  
615/617  FAIL 2
  d:\usr\Tatsu\mingwhome\octaves\octavesrc\octave-3.4.0\src\dirfns.cc  PASS    
0/1    FAIL 1
  d:\usr\Tatsu\mingwhome\octaves\octavesrc\octave-3.4.0\src\ov-fcn-handle.cc  
PASS    2/3    FAIL 1

Fixed test scripts:

  test_sparse.m .......................................... PASS 1202/1204 FAIL 2
  test_io.m .............................................. PASS   66/68   FAIL 2
  test_prefer.m .......................................... PASS   27/29   FAIL 2
  test_system.m .......................................... PASS   83/84   FAIL 1

Summary:

  PASS   6891
  FAIL     11

There was 1 expected failure (see fntests.log for details).

Expected failures are known bugs.  Please help improve Octave
by contributing fixes for them.

There were 11 skipped tests (see fntests.log for details).
Skipped tests are features that are disabled in this version of Octave
because the needed libraries were not present when Octave was built.

577 (of 892) .m files have no tests.

80 (of 146) .cc files have no tests.

Please help improve Octave by contributing tests for
these files (see the list in the file fntests.log).

# 
Compared to the fntests for default branch, number of the items in the fntests 
in 3.4 is larger tha
n that in the default source.

I would like report the fail results. I would like to register them octave bug 
tracker with labeling
to 3.4.0.  Is this OK?

Regards

Tatsuro


--------------------------------------
Get the new Internet Explorer 8 optimized for Yahoo! JAPAN
http://pr.mail.yahoo.co.jp/ie8/


reply via email to

[Prev in Thread] Current Thread [Next in Thread]