fntests errors on mingw-Octave 1:dispatch.cc

[Michael Goffioul]

On 1/2/08, Tatsuro MATSUOKA <tmacchant at yahoo.co.jp> wrote:
> Hi
>
> I have some errors in fntests  mingw-Octave 3.0.0.
>  octave-3.0.0\src/DLD-FUNCTIONS/dispatch.cc  PASS   11/13   FAIL 2
>  octave-3.0.0\src/DLD-FUNCTIONS/rand.cc  PASS   56/57   FAIL 1 known
>  octave-3.0.0\src/ov-fcn-handle.cc  PASS    2/3    FAIL 1
>  octave-3.0.0\scripts/general/bitcmp.m  PASS   14/15
>  FAIL 1
>
>  test_system.m .......................................... PASS  112/126  FAIL 14
>
>  + test_io.m freezes during the test.
>
> I would like remove them one by one.

You probably have more or less the same failures as I have with
MSVC. See below for a mail I sent just before the 3.0.0 release.
Most of the failures are "expected" under Win32 system, mainly
because the test itself is too UNIX oriented.

Michael.

===============================================

The package compiles fine under MSVC. I ran the test suite and
here are the results:

dispatch.cc - 2 failures
These are due to the fact the argument to
"system" is not run into a shell, so something like
system("echo 'something'>file.out") does not generate file.out; hence
the dispatch tests that use this trick to produce temporary m-file fail.

general/bitcmp.m - 1 failure
 ***** assert(bitcmp(A,Amax),bitor(bitshift(1,Amax-1),bitshift(1,Amax-2)));
!!!!! test failed
error: assert (bitcmp (A, Amax),bitor (bitshift (1, Amax - 1),
bitshift (1, Amax - 2))) expected
6.7554e+015
but got
1.1259e+016
values do not match
shared variables {
 Amax =  53
 Bmax = 9.0072e+015
 A = 2.2518e+015
}

test_string - 1 failure
This is due to the fact that under MSVC: isprint(setstr(9)) == 1,
while the test expects 0.

test_system - 14 failures
The reasons are various:
- stat(filesep) fails; what works is stat('\\') or stat('C:\')
- getpwuid, getprgp, getppid, getpwent, getgrent are not implemented
- doing "cd /" and "pwd ()" does not give you "/", but something
including the current drive letter (like "d:\")

In summary, almost all failures are "expected" under MSVC. The only
one that could be problematic is the one related to bitcmp. However,
as I'm no expert, I don't really understand what's going on.