help-octave
[Top][All Lists]
Advanced

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

Some failed tests in Octave 3.3.53 [more details]


From: José Luis García Pallero
Subject: Some failed tests in Octave 3.3.53 [more details]
Date: Thu, 4 Nov 2010 17:49:24 +0100

Hello,
I've compiled versions 3.3.51 and the current hg sources. I'll repeat
some of the text from the previous mail.

I'm trying to install testing versions of Octave (3.3.51, 3.3.53 and
hg sourves) in order to use the package octcdf from octave-forge. I'm
working with a centrino laptop (pentium-m 'banias' 1.3 GHz) running
Debian GNU/Linux unstable.
The compilation proccess runs OK, but I've found problems in make
check step (different problems for different versions). The problems
are:

1. Tests failed in time.cc (FAIL 2). Apparently the function 'datestr'
has problems. This error appears in versions 3.3.53 and current
mercurial sources, but not in 3.3.51. The log file says:

>>>>> processing /home/topo/Desktop/octave-3.3.53/src/DLD-FUNCTIONS/time.cc
 ***** assert (datestr (datenum (1901, 1, 1), 0), "01-Jan-1901 00:00:00")
!!!!! test failed
assert (datestr (datenum (1901, 1, 1), 0),"01-Jan-1901 00:00:00") expected
01-Jan-1901 00:00:00
but got
01-Jan-1970 00:59:59
 ***** assert (datestr (datenum (1795, 1, 1), 0), "01-Jan-1795 00:00:00")
!!!!! test failed
assert (datestr (datenum (1795, 1, 1), 0),"01-Jan-1795 00:00:00") expected
01-Jan-1795 00:00:00
but got
01-Jan-1970 00:59:59

If I do the tests by hand or via test time, the results are the same
than make check

**********************************************************************************************************

2. Test failed in chol.cc (FAIL 1). This error appears in all
versions: 3.3.51, 3.3.53 and current hg source code. The log file
says:

!!!!! test failed
assert (norm (R1 - R, Inf) < 1e1 * eps) failed
shared variables {
 A =

    0.436997  -0.131721   0.124120  -0.061673
   -0.131721   0.738529   0.019851  -0.140295
    0.124120   0.019851   0.354879  -0.059472
   -0.061673  -0.140295  -0.059472   0.600939

 u =

    0.98950
    0.39844
    0.63484
    0.13351

 Ac =

  Columns 1 through 3:

    0.55855 + 0.00000i  -0.16621 - 0.03153i   0.01079 + 0.02364i
   -0.16621 + 0.03153i   0.67601 + 0.00000i   0.00115 - 0.04755i
    0.01079 - 0.02364i   0.00115 + 0.04755i   0.62631 + 0.00000i
   -0.02768 + 0.01861i   0.01460 - 0.02476i  -0.15858 + 0.07198i

  Column 4:

   -0.02768 - 0.01861i
    0.01460 + 0.02476i
   -0.15858 - 0.07198i
    0.60342 + 0.00000i

 uc =

    0.54267 + 0.91519i
    0.99647 + 0.43141i
    0.83760 + 0.68977i
    0.39160 + 0.90378i

If I do test chol the results are the same than for make check

But if I run the compiled source via ./run-octave before the
installation and assign the variables Ac and uc the results are:

For 3.3.51: assert(norm(R1 - R,Inf) < 1e1*eps) not produces error
For 3.3.53: assert(norm(R1 - R,Inf) < 1e1*eps) not produces error
For hg source: assert(norm(R1 - R,Inf) < 1e1*eps) not produces error

Is it a bug? Does make check some different that the tests made by hand?

******************************************************************************************

3. The make check process stops (segmentation fault) when testing
imread.m. If I run ./run-octave and try test imread I obtain a bit
more information:

warning: your version of GraphicsMagick limits images to 8 bits per pixel
ocal/bin: magick/pixel_cache.c:2765: ModifyCache: Assertion
`image->cache != (Cache) ((void *)0)' failed.
panic: Aborted -- stopping myself...

In Octave stable 3.2.4, test imread produces a segmentation fault too
but a bit different message:

octave: magick/semaphore.c:525: LockSemaphoreInfo: Assertion
`semaphore_info != (SemaphoreInfo *) ((void *)0)' failed.
panic: Aborted -- stopping myself...

*****************************************************************************************

Are these fails known or could be bugs? About imread, my version of
graphicsmagick is the one provided in the debian unstable
repositories, 1.3.12, that is, the latest stable.

Other thing. When I start with ./run-octave (3.3.51 and hg src) a
warning related with my .octaverc appears:

warning: /home/topo/.octaverc: possible Matlab-style short-circuit
operator at line 117, column 30

In line 117 of my octaverc says

if strcmp(PAGER(),'less')&isempty(getenv('LESS'))
       PAGER_FLAGS(['-e -X -P"-- less ?pB(%pB\\%):--. (f)orward, (b)ack, ',...
                    '(q)uit$"']);
end

Is '&' not more the 'and' operator in octave? With current 3.2.4
varsion no warning appears.

Thanks

--
*****************************************
José Luis García Pallero
address@hidden
(o<
/ / \
V_/_
Use Debian GNU/Linux and enjoy!
*****************************************



-- 
*****************************************
José Luis García Pallero
address@hidden
(o<
/ / \
V_/_
Use Debian GNU/Linux and enjoy!
*****************************************



reply via email to

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