Dear Sébastien,

Thanks a lot. I cannot replicate the third crash on Windows. On Linux, I get

*** Error in `/usr/local/bin/octave-cli-4.2.1': double free or corruption (!prev): 0x000000000                                                                          26faad0 ***

panic: Aborted -- stopping myself...

attempting to save variables to 'octave-workspace'...

save to 'octave-workspace' complete

Aborted

The first one seems to be a bug in Octave. I filed a bug report at https://savannah.gnu.org/bugs/index.php?51198

Best,

Johannes

Von: Dev [mailto:dev-bounces@dynare.org] Im Auftrag von Sébastien Villemot
Gesendet: Mittwoch, 7. Juni 2017 12:10
An: dev@dynare.org
Betreff: Re: [DynareDev] Beta release of 4.5.0

Dear all,

Le lundi 29 mai 2017 à 23:46 +0200, Stéphane Adjemian a écrit :

I do not receive integration tests reports for Octave since ages... I don't know why. Before the disappearance of the reports we had some failing tests, it would be nice to fix them. The difficulty with the Octave testsuite is that it often never ends. Some mod files, not always the same, run forever. I am convinced that this is not a bug in these files but rather a consequence of the memory leaks Ferhat has to fix in bytecode.

I have run the testsuite for Octave. The environment is Debian unstable, with Octave 4.2.1 from Debian experimental, and a few Octave forge packages recompiled by hand. The commit tested is d608588ef2 on the 4.5 branch.

Basically there are only 3 test failures :

• estimation/fs2000_calibrated_covariance.mod
• estimation/fs2000_model_comparison.mod
• kalman_filter_smoother/compare_results_simulation/fs2000_ML.mod

The first and the third ones are crashes in Octave. I am going to investigate them. The second failure is simply the consequence of the first failure (the second test needs the output of the first one).

-- 

Sébastien Villemot
Économiste
Sciences Po, OFCE