Re: Unmaintained packages - becoming a maintainer?

[Oliver Heimlich]

On 21.05.2015 12:05, address@hidden wrote:
> > Le 21/05/2015 07:15, address@hidden a écrit :
...
> > In the same
> > spirit, you should look at the recent effort by Oliver Heimlich:
> >
> > http://wiki.octave.org/Octave-Forge#GNU_Octave_4.0_compatibility_assessment.
>
> That page covers some of the same ground I am looking at, Olivers page
> should be considered definitive at the moment, while any of my results are
> a work-in-progress.

The list in the wiki is rather specific for tracking the status for the 
mxe-build (Windows) of Octave version >= 4. As soon as you have sorted 
out the errors in your CI and the questions for the mxe-build are 
resolved, the table in the wiki is going to die out.

The table has been created mostly by hand and the help of the following 
script, which finds all the tests in each package (for example, the 
number of unit tests in the interval package should be over 9000). The 
__run_test_suite__ searches recursively for tests. The test logs are 
very useful if any tests fail.


# Install any packages to be tested
...
# Test any installed packages
packages = pkg ("list");
for i = 1 : numel (packages)
    pkg unload all
    pkg ("load", packages {i}.name)
    __run_test_suite__ ({packages{i}.dir}, {})

    # Archive the test log
    movefile ('fntests.log', [packages{i}.name, '-', 
packages{i}.version, ...
        '-fntests.log'], 'f');
endfor



A while ago, I have submitted two patches (bugs 41215 and 41298), which 
would also provide a “pkg test” command and would allow testing of 
oct-files. Maybe these are useful too.


In your table, very few tests pass. Did you load the packages before 
testing?