Re: octave image test failures with octave 4.0.1

[Carnë Draug]

On 23 March 2016 at 15:29, Orion Poplawski <address@hidden> wrote:
> I've updated octave to 4.0.1 in Fedora Rawhide.  Now octave-image builds are
> failing running the tests.  See
> https://kojipkgs.fedoraproject.org/work/tasks/2849/13432849/build.log
> for full logs.
>
>   graythresh.m ...........................................warning: Octave
> language extension used: ! used as operator near line 93 offile
> /usr/share/octave/4.0.1/m/plot/draw/hist.m
> warning: Octave language extension used: ++ used as operator near line 107
> offile /usr/share/octave/4.0.1/m/plot/draw/hist.m
> warning: Octave language extension used: != x)) used as operator near line
> 120 offile /usr/share/octave/4.0.1/m/plot/draw/hist.m
> warning: Octave language extension used: ! used as operator near line 142
> offile /usr/share/octave/4.0.1/m/plot/draw/hist.m
> warning: Octave language extension used: ! used as operator near line 157
> offile /usr/share/octave/4.0.1/m/plot/draw/hist.m
> warning: Octave language extension used: ++ used as operator near line 159
> offile /usr/share/octave/4.0.1/m/plot/draw/hist.m
> warning: Octave language extension used: ! used as operator near line 160
> offile /usr/share/octave/4.0.1/m/plot/draw/hist.m
> warning: comparing complex numbers is not supported in Matlab
> warning: comparing complex numbers is not supported in Matlab
> panic: impossible state reached in file 'corefcn/error.cc' at line 1470
> panic: Aborted -- stopping myself...
> attempting to save variables to 'octave-workspace'...
> save to 'octave-workspace' complete
> /var/tmp/rpm-tmp.TahDd0: line 32:   724 Aborted                 (core
> dumped) octave -H -q --no-window-system --no-site-file --eval
> "warning('off','all');pkg('prefix','/builddir/build/BUILDROOT/octave-image-2.4.1-1.fc25.i386/usr/share/octave/packages','/builddir/build/BUILDROOT/octave-image-2.4.1-1.fc25.i386/usr/lib/octave/packages');pkg('global_list',fullfile('/builddir/build/BUILDROOT/octave-image-2.4.1-1.fc25.i386/usr/share/octave','octave_packages'));pkg('local_list',fullfile('/builddir/build/BUILDROOT/octave-image-2.4.1-1.fc25.i386/usr/share/octave','octave_packages'));pkg('install','-nodeps','-verbose','/var/tmp/octave-image-2.4.1-1.fc25.i386/image-2.4.1.tar.gz');pkg('load','image');runtests('/builddir/build/BUILDROOT/octave-image-2.4.1-1.fc25.i386/usr/share/octave/packages/image-2.4.1');unlink(pkg('local_list'));unlink(pkg('global_list'));"
>
> Is anyone else seeing this?
>
> There were a couple of other updates in addition to octave, so it may be
> something else triggering it.
>

I don't see this.  Is the image package the only package where this happens?
All the warnings I see is about Matlab compatibility (use of Octave unique
operators).

I see that it's disabling all warnings (obviously not working) before running
the tests.  Why is that?

On a side note, you can use double quotes so instead of:

    --eval 'warning('\''off'\'','\''all'\'');pkg('\''prefix'\'', ...

you could write:

    --eval 'warning("off","all");pkg("prefix", ...

Carnë