Re: Heisenbug on Windows with current dev sources

[John W. Eaton]

On 4/12/19 2:48 PM, PhilipNienhuis wrote:
> John W. Eaton wrote

> > Any ideas about how to debug this problem?
>
> No idea, not even a clue, sorry, but since yesterday or so I see the same.
> I configured with --ccache and --enable-fortran-in64 rather than
> -enable-windows-64 (isn't the latter implied by --enable-64?), otherwise the
> same as your options.
>
> runtests ('/full/path/to/..../fixed/publish/') doesn't crash, nor do I get a
> crash running all *.cc-tst files in tests/.../fixed/ manually - actually in
> a for loop along the lines of
>
> dirout = dir();
> for ii=1:numel_dirout
>    clear -g;
>    test dirout(ii).name
> endfor
>
> JohnD once reported he could avoid a similar "Heisencrash" in
> __run_test_suite__.m by running the fixed tests first.

Yeah, so I'm thinking that there is a bug somewhere, but triggering it 
is not simple and it may be specific to some system-dependent code that 
is only enabled on Windows.

> Lately I see 2 FAILs in nest.tst and 4 earlier FAILs in a (AFAICS)
> libinterp/ function. Could it be that the recent work in the parser affected
> __run_test_suite__.m's functionality?
> See here:
> :
> fixed\fcn-handle\static-method.tst ............................. PASS    4/4
> ..n-handle-derived-resolution\fcn-handle-derived-resolution.tst  PASS    3/7
>                                                                     FAIL    4
> fixed\local-functions\local_functions.tst ...................... PASS    1/1
> fixed\nest\nest.tst ............................................ PASS
> 20/23
>                                                                     FAIL    2
>                                                                REGRESSION   1

I think those are due to files omitted from the tar file distribution 
and are fixed by the following change:

http://hg.savannah.gnu.org/hgweb/octave/rev/2e364bd8efb5

jwe