[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Testing MXE-Octave
From: |
PhilipNienhuis |
Subject: |
Re: Testing MXE-Octave |
Date: |
Tue, 12 Feb 2013 10:37:27 -0800 (PST) |
PhilipNienhuis wrote
> Torsten wrote:
> :
> <snip>
> :
>> Other problems I noticed with the MXE build:
>> - using at least 30% of cpu time even when idle
Confirmed, on a quadcore CPU OctaveMXE (based on 3.7.1) uses around 21% CPU
time.
>> - only few fonts usable in the console due to wrong cursor positions
Yep, only Lucida Console font seems to work OK.
With all other fonts, lines get wrapped at ~60, ~40 or even ~20 chars
Underline cursor doesn't work (I only get a block cursor, + with many fonts
it is several tens of char positions to the right).
Cursor blinking doesn't work.
>> I think these problems are not specific to the MXE cross build but
>> generally to windows builds of the gui.
Well... the Octave GUI consistently crashes on exit (on Win7 64bit). That
didn't happen with the last MinGW build I made (~ 2 months ago).
Another issue (perhaps more for the bug tracker):
Editor doesn't work OK (also on Linux):
- Not yet coupled with EDITOR function
- Can't be made to pop up after "edit" command
- In debug mode, step etc buttons get greyed out after first click until the
next restart.
Other tests:
octave-cli.exe:1> pwd
ans = D:\Octave\octave-2013-01-16-21-20
octave-cli.exe:2> cd share/octave/3.7.1/m/testfun
octave-cli.exe:3> runtests
Processing files in .:
:
<snip>
speed.m ................................................ ***** test
[order, n, T_f1, T_f2] = speed ("airy (x)", "x = rand (n, 10)", [100,
1000]);
assert (isstruct (order));
assert (size (order), [1, 1]);
assert (fieldnames (order), {"p"; "a"});
assert (isnumeric (n));
assert (length (n) > 10);
assert (isnumeric (T_f1));
assert (size (T_f1), size (n));
assert (isnumeric (T_f2));
assert (length (T_f2) > 10);
!!!!! test failed
speed: All running times were zero.
warning: test: some elements in list of return values are undefined
:
<snip>
quadgk.m ............................................... ***** assert
(quadgk (@(z) log
(z),1+1i,1+1i, "WayPoints", [1-1i, -1,-1i, -1+1i]), -pi * 1i, 1e-6)
!!!!! test failed
max_recursion_depth exceeded
warning: test: some elements in list of return values are undefined
quadv.m ................................................warning: division
by zero
warning: division by zero
PASS 5/5
:
<snip>
logm.m .................................................warning: logm:
principal matrix
logarithm is not defined for matrices with negative eigenvalues; computing
non-principal logarithm
PASS 10/10
:
<snip>
pcg.m ..................................................warning: pcg:
eigenvalue estimate failed: iteration converged too fast
PASS 4/4
:
<snip>
svds.m ................................................. ***** testif
HAVE_ARPACK
[u2,s2,v2,flag] = svds (A,k);
s2 = diag (s2);
assert (flag, !1);
assert (s2, s(end:-1:end-k+1), 1e-10);
!!!!! test failed
could not find library or dependents:
D:\Octave\octave-2013-01-16-21-20\lib\octave\3.7.1\o
ct\i686-pc-mingw32\eigs.oct
warning: test: some elements in list of return values are undefined
:
<snip>
hankel.m ...............................................warning: hankel:
column wins anti-diagonal conflict
PASS 11/11
:
<snip>
speed.m ................................................ ***** test
[order, n, T_f1, T_f2] = speed ("airy (x)", "x = rand (n, 10)", [100,
1000]);
assert (isstruct (order));
assert (size (order), [1, 1]);
assert (fieldnames (order), {"p"; "a"});
assert (isnumeric (n));
assert (length (n) > 10);
assert (isnumeric (T_f1));
assert (size (T_f1), size (n));
assert (isnumeric (T_f2));
assert (length (T_f2) > 10);
!!!!! test failed
speed: All running times were zero.
warning: test: some elements in list of return values are undefined
Philip
--
View this message in context:
http://octave.1599824.n4.nabble.com/GUI-doesn-t-appear-when-using-run-octave-tp4644161p4649801.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.
- Re: Testing MXE-Octave, (continued)
- Re: Testing MXE-Octave, Torsten, 2013/02/12
- Re: Testing MXE-Octave, Philip Nienhuis, 2013/02/12
- Re: Testing MXE-Octave, Daniel J Sebald, 2013/02/12
- Re: Testing MXE-Octave, PhilipNienhuis, 2013/02/12
- using timers in the GUI (was: Re: Testing MXE-Octave), John W. Eaton, 2013/02/18
- Re: using timers in the GUI (was: Re: Testing MXE-Octave), Jacob Dawid, 2013/02/18
- Re: using timers in the GUI, Torsten, 2013/02/18
- Re: using timers in the GUI, Daniel J Sebald, 2013/02/18
- Re: using timers in the GUI, Jacob Dawid, 2013/02/19
- Re: using timers in the GUI, Daniel J Sebald, 2013/02/19
- Re: Testing MXE-Octave,
PhilipNienhuis <=
- Re: Testing MXE-Octave, Torsten, 2013/02/12
- Re: Testing MXE-Octave, Torsten, 2013/02/16
- Re: Testing MXE-Octave, Daniel J Sebald, 2013/02/12