RC1 Candidate

classic Classic list List threaded Threaded
58 messages Options
123
Reply | Threaded
Open this post in threaded view
|

Re: RC1 Candidate

mmuetzel
Am Sonntag, 27. Januar 2019 um 18:47 Uhr schrieb "Anadi Kashyap":
> I'll reattach it to this email. Hope it's not empty this time heh

Thanks. This time it went through.
It looks like the additional errors and the regression are due to a too old texinfo.

Markus

Reply | Threaded
Open this post in threaded view
|

Re: RC1 Candidate

Anadi Kashyap
In reply to this post by apjanke-floss


On Sun, Jan 27, 2019 at 10:30 PM Andrew Janke <[hidden email]> wrote:


On 1/27/19 9:08 AM, Anadi Kashyap wrote:
>
> On Sun, Jan 27, 2019 at 7:28 PM "Markus Mützel" <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>     Am 27. Januar 2019 um 14:13 Uhr schrieb "Anadi Kashyap":
>      > On Sun, Jan 27, 2019 at 5:59 PM Torsten <[hidden email]
>     <mailto:[hidden email]>[mailto:[hidden email]
>     <mailto:[hidden email]>]> wrote:On 27.01.19 13:26, Anadi Kashyap
>     wrote:
>      > >
>      > > It should be printed to stdout at the end of all tests.
>      > >
>      > > Torsten
>      >
>      > Oh. Mine doesn't do that.
>      >
>      > ----- skipped test (missing feature)
>      >
>      > >>>>> processing /Users/katokateki/octave-5.0.90/test/leftdiv.tst
>      > >>>>> processing
>     /Users/katokateki/octave-5.0.90/test/line-continue.tst
>      > >>>>> processing
>     /Users/katokateki/octave-5.0.90/test/logical-index.tst
>      > >>>>> processing /Users/katokateki/octave-5.0.90/test/null-assign.tst
>      > >>>>> processing /Users/katokateki/octave-5.0.90/test/parser.tst
>      > >>>>> processing /Users/katokateki/octave-5.0.90/test/prefer.tst
>      > >>>>> processing /Users/katokateki/octave-5.0.90/test/range.tst
>      > >>>>> processing /Users/katokateki/octave-5.0.90/test/recursion.tst
>      > >>>>> processing /Users/katokateki/octave-5.0.90/test/return.tst
>      > >>>>> processing
>     /Users/katokateki/octave-5.0.90/test/single-index.tst
>      > >>>>> processing /Users/katokateki/octave-5.0.90/test/slice.tst
>      > >>>>> processing /Users/katokateki/octave-5.0.90/test/struct.tst
>      > >>>>> processing /Users/katokateki/octave-5.0.90/test/switch.tst
>      > >>>>> processing /Users/katokateki/octave-5.0.90/test/system.tst
>      > >>>>> processing /Users/katokateki/octave-5.0.90/test/transpose.tst
>      > >>>>> processing /Users/katokateki/octave-5.0.90/test/try.tst
>      > >>>>> processing /Users/katokateki/octave-5.0.90/test/unwind.tst
>      > >>>>> processing /Users/katokateki/octave-5.0.90/test/while.tst
>      >
>      > That's all. Sorry, I'm new to this. Any help is appreciated.
>
>     What you have pasted looks like the content of fntests.log.
>     Do you see any output in the terminal (or whatever that is called on
>     Mac) while running "make check"? It should be looking similarly to this:
>
>     --snip--
>        struct.tst .....................................................
>     PASS   47/47
>        switch.tst .....................................................
>     PASS    8/8
>        system.tst .....................................................
>     PASS  103/103
>        transpose.tst ..................................................
>     PASS   16/16
>        try.tst ........................................................
>     PASS   18/18
>        unwind.tst .....................................................
>     PASS    2/2
>        while.tst ......................................................
>     PASS    6/6
>
>     Summary:
>
>        PASS                            15430
>        FAIL                                0
>        XFAIL (reported bug)               24
>        SKIP (missing feature)            124
>        SKIP (run-time condition)          12
>
>     --snip--
>
>     Markus
>
> What I pasted was actually the last bit of the output on my terminal.
>
> If it's of any help, I get "Unknown command `codequoteundirected'." a
> lot during the make check. I have the latest texinfo according to
> brew... A known bug simply tells me to ignore it though.

That "codequoteundirected" stuff is because octave is running against a
too-old version of Texinfo. Even though you have a new-enough Texinfo
installed via Homebrew, that version is not on the $PATH by default,
because Homebrew's policy is to avoid shadowing system-provided
packages. So octave doesn't see it.

To make Octave use the newer Texinfo, either add it to your path before
running octave, like this:

PATH="$(brew --prefix texinfo)/bin:$PATH"
octave

Or modify your octave install to use it all the time by adding this to
the /usr/local/share/octave/site/m/startup/octaverc file for your octave
installation (replace /usr/local with wherever you actually installed
octave):

makeinfo_program ("/usr/local/opt/texinfo/bin/makeinfo");

(There, replace "/usr/local/opt/texinfo" with whatever your "brew
--prefix texinfo" actually is.)

Cheers,
Andrew
Worked like a charm, thanks.

Ran make check again:

Summary:

  PASS                            15466
  FAIL                                3
  XFAIL (reported bug)               44
  SKIP (missing feature)             37
  SKIP (run-time condition)          40 

Reply | Threaded
Open this post in threaded view
|

Re: RC1 Candidate

tmacchant
In reply to this post by Dmitri A. Sergatskov

>On Sat, Jan 26, 2019 at 5:39 PM Tatsuro MATSUOKA <[hidden email]> wrote:
>
>
>>  PASS                            15516
>>  FAIL                                2
>>  XFAIL (reported bug)               23
>>  SKIP (missing feature)             37
>>  SKIP (run-time condition)          12
>>
>>  image/getframe.m ............................................... PASS    0/2  
>>                                                                   FAIL    2
>>
>
>
>Tatsuro,
>
>
>I suspect you run it remotely (through ssh) and those are due to the problems you
>are having with X11 forwarding. You may try to re-run it with virtual frame-buffer:
>
>
>xvfb-run -a -s '-screen 0 640x480x24' ./run-octave -q -f
>octave:1> plot(1:10)
>
>(no actual plot is produced)
>
>octave:2> test image/getframe
>PASSES 2 out of 2 tests

>Dmitri.
>--


>I suspect you run it remotely (through ssh) and those are due to the problems you
>are having with X11 forwarding.

Yes.

>xvfb-run -a -s '-screen 0 640x480x24' ./run-octave -q -f 
>octave:1> plot(1:10) 
>
>(no actual plot is produced)
>
>octave:2> test image/getframe 


***** testif HAVE_QT_OFFSCREEN; have_window_system ()
 hf = figure ("visible", "off");
 unwind_protect
   pos = get (hf, "position");
   assert (size (getframe (hf).cdata)(1:2), pos(4:-1:3));
 unwind_protect_cleanup
   close (hf);
 end_unwind_protect
!!!!! test failed
ASSERT errors for:  assert (size (getframe (hf).cdata) (1:2),pos (4:-1:3))

  Location  |  Observed  |  Expected  |  Reason
    (1)           0           420        Abs err 420 exceeds tol 0 by 4e+02
    (2)           0           560        Abs err 560 exceeds tol 0 by 6e+02


Tatsuro

Reply | Threaded
Open this post in threaded view
|

Re: RC1 Candidate

Rik-4
In reply to this post by mmuetzel
On 01/27/2019 06:11 AM, "Markus Mützel" wrote:
> Am 26. Januar 2019 um 16:25 Uhr schrieb "Rik":
>> The first release candidate for Octave version 5.1 is available at
>> ftp://alpha.gnu.org/gnu/octave/.
>>
>> I've tried it on my vanilla Linux system (./configure, make) and building
>> is just fine.  Running 'make check' passes with no failed tests.
>>
>> Please download and experiment on other systems.
> Will there be official Windows installers for the release candidate?

jwe makes the release candidates.  I assume he will make an MXE version of
5.0.90.

--Rik

> Markus
>
>
>


Reply | Threaded
Open this post in threaded view
|

Re: RC1 Candidate

Anadi Kashyap
In reply to this post by apjanke-floss


On Sun, Jan 27, 2019 at 12:52 PM Andrew Janke <[hidden email]> wrote:


If anyone wants to test it on macOS, I've added the 5.1 RC1 release as
the devel release for the octave-octave-app Homebrew formula.
https://github.com/octave-app/homebrew-octave-app-bases/blob/15b361e82d027d145183d645e50af03db35dc662/Formula/octave-octave-app.rb

To use it:

brew tap octave-app/octave-app-bases

Are you sure it's not supposed to be "brew tap octave-app/homebrew-octave-app-bases"?  
"octave-app/octave-app-bases" doesn't exist..
Reply | Threaded
Open this post in threaded view
|

Re: RC1 Candidate

apjanke-floss


On 1/28/19 12:23 AM, Anadi Kashyap wrote:

>
>
> On Sun, Jan 27, 2019 at 12:52 PM Andrew Janke <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>
>
>     If anyone wants to test it on macOS, I've added the 5.1 RC1 release as
>     the devel release for the octave-octave-app Homebrew formula.
>     https://github.com/octave-app/homebrew-octave-app-bases/blob/15b361e82d027d145183d645e50af03db35dc662/Formula/octave-octave-app.rb
>
>     To use it:
>
>     brew tap octave-app/octave-app-bases
>
> Are you sure it's not supposed to be "brew tap
> octave-app/homebrew-octave-app-bases"?
> "octave-app/octave-app-bases" doesn't exist..

I am sure. The repo name is octave-app/homebrew-octave-app-bases, but
the tap name is octave-app/octave-app-bases. Homebrew implicitly adds
the "homebrew-" prefix to convert a tap name to the name of the repo
that stores its data.

$ brew tap octave-app/octave-app-bases
                                                  master
==> Tapping octave-app/octave-app-bases
Cloning into
'/usr/local/Homebrew/Library/Taps/octave-app/homebrew-octave-app-bases'...
remote: Enumerating objects: 180, done.
remote: Counting objects: 100% (180/180), done.
remote: Compressing objects: 100% (106/106), done.
[...]

Cheers,
Andrew

Reply | Threaded
Open this post in threaded view
|

Re: RC1 Candidate

Anadi Kashyap


On Mon, Jan 28, 2019 at 10:56 AM Andrew Janke <[hidden email]> wrote:


On 1/28/19 12:23 AM, Anadi Kashyap wrote:
>
>
> On Sun, Jan 27, 2019 at 12:52 PM Andrew Janke <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>
>
>     If anyone wants to test it on macOS, I've added the 5.1 RC1 release as
>     the devel release for the octave-octave-app Homebrew formula.
>     https://github.com/octave-app/homebrew-octave-app-bases/blob/15b361e82d027d145183d645e50af03db35dc662/Formula/octave-octave-app.rb
>
>     To use it:
>
>     brew tap octave-app/octave-app-bases
>
> Are you sure it's not supposed to be "brew tap
> octave-app/homebrew-octave-app-bases"?
> "octave-app/octave-app-bases" doesn't exist..

I am sure. The repo name is octave-app/homebrew-octave-app-bases, but
the tap name is octave-app/octave-app-bases. Homebrew implicitly adds
the "homebrew-" prefix to convert a tap name to the name of the repo
that stores its data.

$ brew tap octave-app/octave-app-bases
                                                  master
==> Tapping octave-app/octave-app-bases
Cloning into
'/usr/local/Homebrew/Library/Taps/octave-app/homebrew-octave-app-bases'...
remote: Enumerating objects: 180, done.
remote: Counting objects: 100% (180/180), done.
remote: Compressing objects: 100% (106/106), done.
[...]

Cheers,
Andrew
Welp, guess it's just me then. 

Wow I checked again and I was typing octave-app-base and not bases :/ 
Thanks for the info. Also, had to uninstall suite-sparse to do the brew install part. Is it normal?
Reply | Threaded
Open this post in threaded view
|

Re: RC1 Candidate

apjanke-floss


On 1/28/19 12:32 AM, Anadi Kashyap wrote:

>
>
> On Mon, Jan 28, 2019 at 10:56 AM Andrew Janke <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>
>     $ brew tap octave-app/octave-app-bases
>                                                        master
>     ==> Tapping octave-app/octave-app-bases
>     Cloning into
>     '/usr/local/Homebrew/Library/Taps/octave-app/homebrew-octave-app-bases'...
>     remote: Enumerating objects: 180, done.
>     remote: Counting objects: 100% (180/180), done.
>     remote: Compressing objects: 100% (106/106), done.
>     [...]
>
>     Cheers,
>     Andrew
>
> Welp, guess it's just me then.
>
> Wow I checked again and I was typing octave-app-base and not bases :/
> Thanks for the info. Also, had to uninstall suite-sparse to do the brew
> install part. Is it normal?

That is not normal. suite-sparse is one of the dependencies of
octave-octave-app, so it should be fine, and in fact required. Perhaps
you had a customized variant of suite-sparse installed? Or maybe you had
installed the OpenBLAS version of suite-sparse from the dpo/openblas tap
at https://github.com/dpo/homebrew-openblas? Because the dpo/openblas
formulae use the same names as core formulae, that could cause conflicts.

Cheers,
Andrew

Reply | Threaded
Open this post in threaded view
|

Re: RC1 Candidate

tmacchant
In reply to this post by Anadi Kashyap
 I have built windows w64-64 binary using mxe-octave.
I tried to execute octave by octave.vbs, the application error (0xc000007b)
appeared.
<http://octave.1599824.n4.nabble.com/file/t131361/ApplicationError.png>
(Sorry for Japanese message.)

However, octave-cli.exe starts up normally.
But this lacks some required environmental settings so that I cannot fully
execute __run_test_suite__.

Have anyone else tried windows build?

Tatsuro



--
Sent from: http://octave.1599824.n4.nabble.com/Octave-Maintainers-f1638794.html

Reply | Threaded
Open this post in threaded view
|

Re: RC1 Candidate

mmuetzel
Am 28. Januar 2019 um 11:07 Uhr schrieb "tmacchant":

>  I have built windows w64-64 binary using mxe-octave.
> I tried to execute octave by octave.vbs, the application error (0xc000007b)
> appeared.
> <http://octave.1599824.n4.nabble.com/file/t131361/ApplicationError.png>
> (Sorry for Japanese message.)
>
> However, octave-cli.exe starts up normally.
> But this lacks some required environmental settings so that I cannot fully
> execute __run_test_suite__.
>
> Have anyone else tried windows build?

This might be due to mis-matched libraries for 32bit and 64bit.
Did you use a clean MXE Octave?

Markus

Reply | Threaded
Open this post in threaded view
|

Re: RC1 Candidate

tmacchant




----- Original Message -----

> From: ""Markus Mützel"" <
> To: tmacchant 
> Cc: octave-maintainers
> Date: 2019/1/28, Mon 19:26
> Subject: Re: RC1 Candidate
>
> Am 28. Januar 2019 um 11:07 Uhr schrieb "tmacchant":
>>   I have built windows w64-64 binary using mxe-octave.
>>  I tried to execute octave by octave.vbs, the application error (0xc000007b)
>>  appeared.
>>
> <http://octave.1599824.n4.nabble.com/file/t131361/ApplicationError.png>
>>  (Sorry for Japanese message.)
>>
>>  However, octave-cli.exe starts up normally.
>>  But this lacks some required environmental settings so that I cannot fully
>>  execute __run_test_suite__.
>>
>>  Have anyone else tried windows build?
>
> This might be due to mis-matched libraries for 32bit and 64bit.
> Did you use a clean MXE Octave?
>
> Markus

This time I used a new directory "mxe-octave-stable" at cloning repository
and all dependencies were freshly constructed.

Tatsuro

Reply | Threaded
Open this post in threaded view
|

Re: RC1 Candidate

tmacchant
\>> 

>>  Am 28. Januar 2019 um 11:07 Uhr schrieb "tmacchant":
>>>    I have built windows w64-64 binary using mxe-octave.
>>>   I tried to execute octave by octave.vbs, the application error
> (0xc000007b)
>>>   appeared.
>>>
>>
> <http://octave.1599824.n4.nabble.com/file/t131361/ApplicationError.png>
>>>   (Sorry for Japanese message.)
>>>
>>>   However, octave-cli.exe starts up normally.
>>>   But this lacks some required environmental settings so that I cannot
> fully
>>>   execute __run_test_suite__.
>>>
>>>   Have anyone else tried windows build?
>>
>>  This might be due to mis-matched libraries for 32bit and 64bit.
>>  Did you use a clean MXE Octave?
>>
>>  Markus
>
> This time I used a new directory "mxe-octave-stable" at cloning
> repository
> and all dependencies were freshly constructed.
>
> Tatsuro


I used the flag

./configure --enable-devel-tools --enable-octave=stable --enable-binary-packages --enable-64 --enable-fortran-int64

Tatsuro

Reply | Threaded
Open this post in threaded view
|

Re: RC1 Candidate

mmuetzel
In reply to this post by tmacchant
Am 28. Januar 2019 um 11:36 Uhr schrieb "Tatsuro MATSUOKA":
> This time I used a new directory "mxe-octave-stable" at cloning repository
> and all dependencies were freshly constructed.

A cross-build from the default branch from Saturday was starting correctly for me.
I'll try a crass-build from the stable branch tonight or tomorrow.

In the meantime: Does starting as administrator make any difference?
Was this with the nsis-installer?

> I used the flag
>
> ./configure --enable-devel-tools --enable-octave=stable --enable-binary-packages --enable-64 --enable-fortran-int64

Do these flags automatically include "--enable-windows-64"?

Markus

Reply | Threaded
Open this post in threaded view
|

Re: RC1 Candidate

mmuetzel
> Am 28. Januar 2019 um 11:36 Uhr schrieb "Tatsuro MATSUOKA":
> > This time I used a new directory "mxe-octave-stable" at cloning repository
> > and all dependencies were freshly constructed.
>
> A cross-build from the default branch from Saturday was starting correctly for me.
> I'll try a crass-build from the stable branch tonight or tomorrow.
>
> In the meantime: Does starting as administrator make any difference?
> Was this with the nsis-installer?
>
> > I used the flag
> >
> > ./configure --enable-devel-tools --enable-octave=stable --enable-binary-packages --enable-64 --enable-fortran-int64
>
> Do these flags automatically include "--enable-windows-64"?
>

To answer my own question: "windows-64" is enabled by default.

The only difference I can remember is that I configured with "--disable-system-opengl" and didn't use "--enable-fortran-int64".
But that shouldn't prevent the GUI from starting at all...

Markus

Reply | Threaded
Open this post in threaded view
|

Re: RC1 Candidate

John W. Eaton
Administrator
In reply to this post by mmuetzel
On 1/27/19 9:11 AM, "Markus Mützel" wrote:

> Am 26. Januar 2019 um 16:25 Uhr schrieb "Rik":
>> The first release candidate for Octave version 5.1 is available at
>> ftp://alpha.gnu.org/gnu/octave/.
>>
>> I've tried it on my vanilla Linux system (./configure, make) and building
>> is just fine.  Running 'make check' passes with no failed tests.
>>
>> Please download and experiment on other systems.
>
> Will there be official Windows installers for the release candidate?

Yes, the installer along with 7z and zip files are on alpha.gnu.org now.

I only made versions for Windows 64 with the usual 32-bit Fortran
integer configuration.

jwe


Reply | Threaded
Open this post in threaded view
|

Re: RC1 Candidate

John Donoghue-3
In reply to this post by Rik-4
>
> Message: 6
> Date: Mon, 28 Jan 2019 10:15:00 -0500
> From: "John W. Eaton" <[hidden email]>
> To: Markus M?tzel <[hidden email]>
> Cc: Octave-Maintainers <[hidden email]>
> Subject: Re: RC1 Candidate
> Message-ID: <[hidden email]>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> On 1/27/19 9:11 AM, "Markus M?tzel" wrote:
> > Am 26. Januar 2019 um 16:25 Uhr schrieb "Rik":
> >> The first release candidate for Octave version 5.1 is available at
> >> ftp://alpha.gnu.org/gnu/octave/.
> >>
> >> I've tried it on my vanilla Linux system (./configure, make) and
building

> >> is just fine.? Running 'make check' passes with no failed tests.
> >>
> >> Please download and experiment on other systems.
> >
> > Will there be official Windows installers for the release candidate?
>
> Yes, the installer along with 7z and zip files are on alpha.gnu.org now.
>
> I only made versions for Windows 64 with the usual 32-bit Fortran
> integer configuration.
>
> jwe
>
>

On Win 10, 64 bit using the  installer:

  PASS                            15502
  FAIL                                1
  XFAIL (reported bug)               26
  SKIP (missing feature)             52
  SKIP (run-time condition)           5

The error:
>>>>> processing
C:\Octave\OCTAVE~1.90\mingw64\share\octave\5.0.90\etc\tests\libinterp\corefc
n\graphics.cc-tst
***** test
 hf = figure ("visible", "off");
 hax = axes ("parent", hf);
 unwind_protect
   hctx1 = uicontextmenu ("parent", hf);
   hctx2 = uicontextmenu ("parent", hf);
   set (hf, "uicontextmenu", hctx2);
   set (hax, "uicontextmenu", hctx2);
   assert (get (hf, "uicontextmenu"), hctx2);
   assert (get (hax, "uicontextmenu"), hctx2);
   assert (get (hf, "children"), [hctx2; hctx1; hax]);
   delete (hctx2);
   assert (get (hf, "uicontextmenu"), []);
   assert (get (hax, "uicontextmenu"), []);
   assert (get (hf, "children"), [hctx1; hax]);
   set (hf, "uicontextmenu", hctx1);
   assert (get (hf, "uicontextmenu"), hctx1);
   set (hf, "uicontextmenu", []);
   assert (get (hf, "uicontextmenu"), []);
   assert (get (hf, "children"), [hctx1; hax]);
 unwind_protect_cleanup
   close (hf);
 end_unwind_protect;
!!!!! test failed
ASSERT errors for:  assert (get (hf, "uicontextmenu"),[])

  Location  |  Observed  |  Expected  |  Reason
     .          O(1x1)       E(0x0)      Dimensions don't match



Reply | Threaded
Open this post in threaded view
|

RE: RC1 Candidate

John Donoghue-3


> -----Original Message-----
> From: JohnD [mailto:[hidden email]]
> Sent: Monday, January 28, 2019 12:19 PM
> To: [hidden email]
> Subject: Re: RC1 Candidate
>
> >
> > Message: 6
> > Date: Mon, 28 Jan 2019 10:15:00 -0500
> > From: "John W. Eaton" <[hidden email]>
> > To: Markus M?tzel <[hidden email]>
> > Cc: Octave-Maintainers <[hidden email]>
> > Subject: Re: RC1 Candidate
> > Message-ID: <[hidden email]>
> > Content-Type: text/plain; charset=utf-8; format=flowed
> >
> > On 1/27/19 9:11 AM, "Markus M?tzel" wrote:
> > > Am 26. Januar 2019 um 16:25 Uhr schrieb "Rik":
> > >> The first release candidate for Octave version 5.1 is available at
> > >> ftp://alpha.gnu.org/gnu/octave/.
> > >>
> > >> I've tried it on my vanilla Linux system (./configure, make) and
> building
> > >> is just fine.? Running 'make check' passes with no failed tests.
> > >>
> > >> Please download and experiment on other systems.
> > >
> > > Will there be official Windows installers for the release candidate?
> >
> > Yes, the installer along with 7z and zip files are on alpha.gnu.org now.
> >
> > I only made versions for Windows 64 with the usual 32-bit Fortran
> > integer configuration.
> >
> > jwe
> >
> >
>
> On Win 10, 64 bit using the  installer:
>
>   PASS                            15502
>   FAIL                                1
>   XFAIL (reported bug)               26
>   SKIP (missing feature)             52
>   SKIP (run-time condition)           5
>
> The error:
> >>>>> processing
> C:\Octave\OCTAVE~1.90\mingw64\share\octave\5.0.90\etc\tests\libinterp\cor
> efc
> n\graphics.cc-tst
> ***** test
>  hf = figure ("visible", "off");
>  hax = axes ("parent", hf);
>  unwind_protect
>    hctx1 = uicontextmenu ("parent", hf);
>    hctx2 = uicontextmenu ("parent", hf);
>    set (hf, "uicontextmenu", hctx2);
>    set (hax, "uicontextmenu", hctx2);
>    assert (get (hf, "uicontextmenu"), hctx2);
>    assert (get (hax, "uicontextmenu"), hctx2);
>    assert (get (hf, "children"), [hctx2; hctx1; hax]);
>    delete (hctx2);
>    assert (get (hf, "uicontextmenu"), []);
>    assert (get (hax, "uicontextmenu"), []);
>    assert (get (hf, "children"), [hctx1; hax]);
>    set (hf, "uicontextmenu", hctx1);
>    assert (get (hf, "uicontextmenu"), hctx1);
>    set (hf, "uicontextmenu", []);
>    assert (get (hf, "uicontextmenu"), []);
>    assert (get (hf, "children"), [hctx1; hax]);
>  unwind_protect_cleanup
>    close (hf);
>  end_unwind_protect;
> !!!!! test failed
> ASSERT errors for:  assert (get (hf, "uicontextmenu"),[])
>
>   Location  |  Observed  |  Expected  |  Reason
>      .          O(1x1)       E(0x0)      Dimensions don't match
>


Running the code of the test manually, I see it failing intermittently.

If I add a pause line into the test:

   delete (hctx2);
   pause(0.1);
   assert (get (hf, "uicontextmenu"), []);

I don't seem to get the fail any more


Reply | Threaded
Open this post in threaded view
|

Re: RC1 Candidate

Avinoam
In reply to this post by tmacchant
tmacchant wrote
I have built windows w64-64 binary using mxe-octave. I tried to execute octave by octave.vbs, the application error (0xc000007b) appeared. <http://octave.1599824.n4.nabble.com/file/t131361/ApplicationError.png> (Sorry for Japanese message.) However, octave-cli.exe starts up normally. But this lacks some required environmental settings so that I cannot fully execute __run_test_suite__. Have anyone else tried windows build? Tatsuro -- Sent from: http://octave.1599824.n4.nabble.com/Octave-Maintainers-f1638794.html
I have build the windows version with the following script:
cd mxe-octave
hg -v pull
hg -v update

PATH=`pwd`/usr/bin:$PATH 
autoconf
./configure --enable-devel-tools --enable-octave=stable --enable-windows-64 --enable-64 
touch src/stable-octave.mk

make nsis-installer 
Avinoam

Sent from the Octave - Maintainers mailing list archive at Nabble.com.
Reply | Threaded
Open this post in threaded view
|

RE: RC1 Candidate

Pantxo
In reply to this post by John Donoghue-3
John Donoghue-3 wrote

>>
>> On Win 10, 64 bit using the  installer:
>>
>>   PASS                            15502
>>   FAIL                                1
>>   XFAIL (reported bug)               26
>>   SKIP (missing feature)             52
>>   SKIP (run-time condition)           5
>>
>> The error:
>> >>>>> processing
>> C:\Octave\OCTAVE~1.90\mingw64\share\octave\5.0.90\etc\tests\libinterp\cor
>> efc
>> n\graphics.cc-tst
>> ***** test
>>  hf = figure ("visible", "off");
>>  hax = axes ("parent", hf);
>>  unwind_protect
>>    hctx1 = uicontextmenu ("parent", hf);
>>    hctx2 = uicontextmenu ("parent", hf);
>>    set (hf, "uicontextmenu", hctx2);
>>    set (hax, "uicontextmenu", hctx2);
>>    assert (get (hf, "uicontextmenu"), hctx2);
>>    assert (get (hax, "uicontextmenu"), hctx2);
>>    assert (get (hf, "children"), [hctx2; hctx1; hax]);
>>    delete (hctx2);
>>    assert (get (hf, "uicontextmenu"), []);
>>    assert (get (hax, "uicontextmenu"), []);
>>    assert (get (hf, "children"), [hctx1; hax]);
>>    set (hf, "uicontextmenu", hctx1);
>>    assert (get (hf, "uicontextmenu"), hctx1);
>>    set (hf, "uicontextmenu", []);
>>    assert (get (hf, "uicontextmenu"), []);
>>    assert (get (hf, "children"), [hctx1; hax]);
>>  unwind_protect_cleanup
>>    close (hf);
>>  end_unwind_protect;
>> !!!!! test failed
>> ASSERT errors for:  assert (get (hf, "uicontextmenu"),[])
>>
>>   Location  |  Observed  |  Expected  |  Reason
>>      .          O(1x1)       E(0x0)      Dimensions don't match
>>
>
>
> Running the code of the test manually, I see it failing intermittently.
>
> If I add a pause line into the test:
>
>    delete (hctx2);
>    pause(0.1);
>    assert (get (hf, "uicontextmenu"), []);
>
> I don't seem to get the fail any more

This is the bug at the origin of the following cset coming back

http://hg.savannah.gnu.org/hgweb/octave/rev/5535267e88ba

Unfortunately
* the bug number in the cset is wrong, and I can't find the original report
ATM
* I really thought making the destruction of graphics objects synchronous
would destroy the last reference and clear this bug, ...t!

Pantxo



--
Sent from: http://octave.1599824.n4.nabble.com/Octave-Maintainers-f1638794.html

Reply | Threaded
Open this post in threaded view
|

Re: RC1 Candidate

mmuetzel
In reply to this post by John W. Eaton
Am 28. Januar 2019 um 16:15 Uhr schrieb "John W. Eaton"
> On 1/27/19 9:11 AM, "Markus Mützel" wrote:
> > Will there be official Windows installers for the release candidate?
>
> Yes, the installer along with 7z and zip files are on alpha.gnu.org now.
>

I installed with the nsis installer and get the attached warning dialog each time I start Octave.
The documentation panels are empty.

The README.html still refers to Octave 4.4.

The graphics_toolkit gnuplot doesn't work. But that is probably already resolved in the meantime.

The "About Octave" dialog isn't translated.

The test suite crashed Octave when I ran it immediately after the installation leaving this entry in the application protocol:
Name der fehlerhaften Anwendung: octave-gui.exe, Version: 0.0.0.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: liboctinterp-7.dll, Version: 0.0.0.0, Zeitstempel: 0x00000000
Ausnahmecode: 0xc00000fd
Fehleroffset: 0x00000000008d2eab
ID des fehlerhaften Prozesses: 0x4628
Startzeit der fehlerhaften Anwendung: 0x01d4b74d042f6f26
Pfad der fehlerhaften Anwendung: C:\Octave\OCTAVE~1.90\mingw64\bin\octave-gui.exe
Pfad des fehlerhaften Moduls: C:\Octave\OCTAVE~1.90\mingw64\bin\liboctinterp-7.dll
Berichtskennung: f8f4a35d-0ba4-4612-a2e6-0b91398c4e45
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:


After a restart, the test suite finished with:
Summary:

  PASS                            15501
  FAIL                                2
  XFAIL (reported bug)               26
  SKIP (missing feature)             52
  SKIP (run-time condition)           5

The failing tests are:
>>>>> processing C:\Octave\OCTAVE~1.90\mingw64\share\octave\5.0.90\etc\tests\libinterp\corefcn\help.cc-tst
***** test
 f = tempname (".", "oct_");
 fcn_name = f(3:end);
 f = [f ".m"];
 unwind_protect
   fid = fopen (f, "w+");
   fprintf (fid, "function z = %s\n z = localfunctions; end\n", fcn_name);
   fprintf (fid, "function z = b(x)\n z = x+1; end\n");
   fprintf (fid, "function z = c(x)\n z = 2*x; end\n");
   fclose (fid);
   d = eval (fcn_name);
   assert (size (d), [2, 1]);
   assert (d{1} (3), 4);
   assert (d{2} (3), 6);
 unwind_protect_cleanup
   unlink (f);
 end_unwind_protect
!!!!! test failed
fprintf: invalid stream number = -1

***** test
 tname = tempname (pwd ());
 unwind_protect
   ## open/close file to create it, equivalent of touch
   fid = fopen (tname, "w");
   fclose (fid);
   [~, fname] = fileparts (tname);
   assert (exist (fullfile (pwd (), fname), "file"), 2);
 unwind_protect_cleanup
   unlink (tname);
 end_unwind_protect
 assert (exist (fullfile (pwd (), "%nonexistentfile%"), "file"), 0);
!!!!! test failed
fclose: invalid stream number = -1
shared variables   scalar structure containing the fields:

    dirtmp = C:\Users\Markus\AppData\Local\Temp
    __var1 =  1


I will try to test on a system with HiDPI monitor and for a user name containing non-ASCII characters within the next few days.

Markus

Octave_5_90_startup.png (8K) Download Attachment
123