[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #55047] Running the test suite causes Octave t
From: |
Philip Nienhuis |
Subject: |
[Octave-bug-tracker] [bug #55047] Running the test suite causes Octave to segfault on Windows |
Date: |
Sun, 18 Nov 2018 12:00:16 -0500 (EST) |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 SeaMonkey/2.48 |
Update of bug #55047 (project octave):
Status: None => Confirmed
_______________________________________________________
Follow-up Comment #1:
On my 64-bit Windows 7 Professional box and Windows 7 Enterprise box at work,
__run_test_suite__ segfaults in the fixed tests section, and fntests.log
always ends with the colormap test.
Insofar it is consistent on just my boxes and ends elsewhere on other people's
boxes I can't say. What might matter there is that I have several binary
patches in my cross-builds (h5read, uitable, matrix right division, shortcut
keys for variable editor).
The individual tests run fine (cd-ing to the fixed test dir and running them
one by one (using "test <blabla>.tst").
I also tried running just the fixed tests:
__run_test_suite_ ({}, {'/path/to/fixed/tests'}, {})
and also then I saw no segfault.
Echo of screen messages attached.
Because of that I didn't pay much attention, but I agree with Markus that
__run_test_suite__ shouldn't end in a segfault.
Maybe the amount of tests, or amount of some type(s) of tests, induces
oversaturation of Octave's resources somewhere?
(file #45482)
_______________________________________________________
Additional Item Attachment:
File name: one_single_and_fixed_tests_bug_55047.txt Size:7 KB
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?55047>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/