octave-maintainers
[Top][All Lists]
Advanced

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

Re: 4.0.1-rc3 candidate on Windows (was Re: 4.0.1-rc2 candidate)


From: Oliver Heimlich
Subject: Re: 4.0.1-rc3 candidate on Windows (was Re: 4.0.1-rc2 candidate)
Date: Tue, 19 Jan 2016 23:04:09 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.5.0

On 19.01.2016 08:50, Oliver Heimlich wrote:
> Hi,
> 
> I have done a brief testing of the installer for Windows.
> 

…

>> warning: autoload: 'pq_interface.oct' is not an absolute file name
>> warning: autoload: 'pq_interface.oct' is not an absolute file name
>> warning: autoload: 'pq_interface.oct' is not an absolute file name
>> warning: autoload: 'pq_interface.oct' is not an absolute file name
>> warning: autoload: 'pq_interface.oct' is not an absolute file name
>> warning: autoload: 'pq_interface.oct' is not an absolute file name
>> warning: autoload: 'pq_interface.oct' is not an absolute file name
>> warning: autoload: 'pq_interface.oct' is not an absolute file name
>> warning: autoload: 'pq_interface.oct' is not an absolute file name

These come from the database package, there seems to be a problem with
the PKG_ADD script.

>> pkg load database
warning: autoload: 'pq_interface.oct' is not an absolute file name
warning: called from

S:\Programme\Octave-4.0.1-rc3\share\octave\packages\database-2.3.2\PKG_ADD a
t line 3 column 1
    load_packages_and_dependencies at line 47 column 5
    load_packages at line 60 column 3
    pkg at line 422 column 7

> I unloaded the packages with shadowing functions (nan, specfun, tsa) and
> did a __run_test_suite__ ({'S:/Programme/Octave-4.0.1-rc3'}, {}).  After
> the test for ghkss (in tisean) took almost an hour, I have canceled the
> tests.  You can find the log (up to this point) attached.
> 
> There have been many test FAILs. I will look into these later this day
> and try to compare with the 4.0.0 release.

Ok, I could sort these out.  In Octave core I manage to get zero FAILs
if I pass the directory of the “fixed” test scripts as a second
parameter to __run_test_suite__.

Regarding the packages:

PACKAGE PASS FAIL XFAIL
communications 457 0 0
control 328 0 0
data-smoothing 0 0 0
database 0 1 0
        (I have no database installed)
dataframe 0 0 0
dicom 0 0 0
financial 161 1 5
        (in fetch.m)
fits 0 0 0
fl-core 0 0 0
fuzzy-logic-toolkit 0 0 0
ga 79 0 0
general 12 0 0
generate_html 0 0 0
geometry 277 3 0
        (python not found)
image 636 3 21
        (in bwmorph.m and fftconv2.m)
instrument-control 0 0 0
interval 9823 0 0
io 11 0 0
linear-algebra 20 0 0
lssa 16 0 0
ltfat 0 0 0
mapping 128 0 0
miscellaneous 381 0 0
nan 31 0 0
netcdf 0 0 0
nurbs 80 0 0
ocs 0 0 0
octcdf 23 0 0
odepkg 404 0 0
optim 16 0 0
quaternion 23 0 0
queueing 263 2 3
        (private function can't be tested)
signal 478 24 1
        (in impinvar.m and invimpinvar.m)
sockets 0 0 0
sparsersb 0 0 0
specfun 6 0 0
splines 81 0 0
statistics 219 25 0
        (various)
stk 1071 1 0
        (in stk_example_kb09.m)
strings 20 0 0
struct 9 0 1
tisean 40+ 8+ 0+
        (tests don't terminate in reasonable time)
tsa 17 2 0
        (in histo.m -- missing mex-files?)
video 0 0 0
windows 0 0 0
zenity 0 0 0

I have attached log files for packages with failing unit tests.

Oliver

Attachment: fntests-financial.log.gz
Description: application/gzip

Attachment: fntests-geometry.log.gz
Description: application/gzip

Attachment: fntests-image.log.gz
Description: application/gzip

Attachment: fntests-queueing.log.gz
Description: application/gzip

Attachment: fntests-signal.log.gz
Description: application/gzip

Attachment: fntests-statistics.log.gz
Description: application/gzip

Attachment: fntests-stk.log.gz
Description: application/gzip

Attachment: fntests-tisean.log.gz
Description: application/gzip

Attachment: fntests-tsa.log.gz
Description: application/gzip


reply via email to

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