[Top][All Lists]

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

[Octave-bug-tracker] [bug #49211] "test syscall" often hangs on Windows

From: Hartmut
Subject: [Octave-bug-tracker] [bug #49211] "test syscall" often hangs on Windows
Date: Wed, 28 Sep 2016 15:58:05 +0000 (UTC)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0


                 Summary: "test syscall" often hangs on Windows
                 Project: GNU Octave
            Submitted by: hardy
            Submitted on: Wed 28 Sep 2016 03:58:03 PM GMT
                Category: Octave Function
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Regression
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.2.0-rc2
        Operating System: Microsoft Windows



I have observed that with the current Octave-4.2.0-rc2 the "test syscall"
sometimes hangs under Windows OS. (With Octave 4.0.3 this still runs fine, its
a regression)

I was able to reduce the underlying test code to a very simple example, that
nearly always creates a "freeze in" of the Octave process on my Windows

more off
for n = 1:10
    # test("syscalls.cc-tst", "verbose")
    # use test code (Win version) directly:
    # (removed many code lines, but "preserve" the hang-up)
   [in, out, pid] = popen2 ('C:\Windows\system32\sort.exe', "/R")
   disp('before waitpid')  # ==> hangs here = during waitpid()
   waitpid (pid)
   disp('after waitpid')

I have the gut feeling, that this bug could have the same origin as several
other bugs reported recently for 4.2.0-rc2 under Windows:
* a "hang-up" of "test copyobj", using gnuplot and the print command (bug
* occasional "hang-ups" of "test legend"  (mentioned somewhere in the bug
* "hang ups" during compare_plot_demos with gnuplot (bug #49180)
The common point is that all those freezing tests call another Windows
executable. Since all the other "freezes" have much more difficult underlying
code, my hope is that this very short test script can help to remove all of
those regression bugs at once.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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