octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #57435] Test suite crashes on Windows on spars


From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #57435] Test suite crashes on Windows on sparse.tst
Date: Fri, 20 Dec 2019 13:09:43 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0

Follow-up Comment #8, bug #57435 (project octave):

If the crash occurs in sparse.tst when running the full test suite but not
when running sparse.tst by itself in a fresh Octave session, then it is
possible that the real problem is in some earlier test that doesn't
immediately cause a crash but corrupts some memory that causes the later crash
in sparse.tst

Does the crash occur if you make something like the following change to remove
the directories for the "integrated test scripts" and run the test suite again
and see if it still crashes?  You can continue bisecting by adding and
removing tests until you find the test directory, file, and then hopefully the
individual test that must be executed before the sparse.tst file to cause the
crash.  Then maybe we can understand exactly what is causing the crash.


diff --git a/scripts/testfun/__run_test_suite__.m
b/scripts/testfun/__run_test_suite__.m
--- a/scripts/testfun/__run_test_suite__.m
+++ b/scripts/testfun/__run_test_suite__.m
@@ -30,7 +30,11 @@ function [pass, fail, xfail, xbug, skip,
   fixedtestdir = fullfile (testsdir, "fixed");
   fcnfiledir = __octave_config_info__ ("fcnfiledir");
   if (nargin == 0)
-    fcndirs = { liboctavetestdir, libinterptestdir, fcnfiledir };
+    fcndirs = { ...
+##                liboctavetestdir, ...
+##                libinterptestdir, ...
+##                fcnfiledir
+              };
     fixedtestdirs = { fixedtestdir };
   endif
   files_with_no_tests = {};


I did this same kind of thing recently to find why publish.tst was suddenly
failing when run as part of the test suite but not when running the test by
itself (bug #57424 and bug #57439).  It took some time but finally uncovered a
problem with function handles caused by a "clear functions" command in the
file test/bug-35881/bug35881.m.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?57435>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]