On Tue, Mar 8, 2016 at 10:08 AM, PhilipNienhuis <address@hidden> wrote:
__run_test_suite__ crashed with
Doug Stewart-4 wrote
> I have successfully built 3 different windows installer versions.
> The latest is default branch, and am about to test it in windows.
>
> My questions are:
>
> 1) What testing should I be doing to help with the next release?
Installation procedure; running it; try to do things you'd do with Octave on
Linux.
> 2) After installing in windows, is there an easy way to do a general test
> of core octave?
A simple
more off;
__run_test_suite__
more or less equals "make check".
Currently Octave-4.1.0+, and probably 4.0.1 as well, still crash after this
(forgot the bug number, IIRC related to GraphicsMagick, but the behavior is
still there) so don't be surprised at that.
MXE-built Octave works wonderfully otherwise, I use it daily.
Fault module name libstdc++-6.dll
This is with the default branch.
> 3) I intend to install all pkgs and test them for compatibility with dev.
> branch, but which pkgs should we test for the next release?
All the ones for which a "src/OF-<package-name>.mk" exists in MXE ?
I have io-2.4.1 release pending, I hope to put it up tonight or tomorrow and
I hope that it can be included in octave-4.0.1 windows binary release.
AFAICS mapping-1.2.1 is included in mxe-octave now, but to (cross)build it
the GDAL library must be inserted as a dependency in stable-octave.mk (and
maybe default-octave.mk) in the mxe-octave/src/ subdir.
As to the dev version of Octave, note bug #47250. JWE mentioned there that
he had fixed a few things, but several OF packages still aren't up-to-date
w.r.t. dev Octave.
Philip
--
View this message in context: http://octave.1599824.n4.nabble.com/Octave-on-windows-testing-tp4675282p4675293.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.