Issue #12445 has been updated by Martin Drst.


Martin Drst wrote:
> `TestSignal#test_exit_action` is another test that hangs in the same way, but from the name, it's not clear whether this is caused by the same bug or not.

Another difference is that for this test, Ctrl-C creates a failure (see below) and moves on, whereas for the others, Ctrl-C isn't of much help.

```
[  63/1101] TestSignal#test_exit_action = 2717.75 s
  1) Failure:
TestSignal#test_exit_action [/cygdrive/c/Data/ruby/test/ruby/test_signal.rb:56]:
[ruby-dev:26128].
Exception raised:
<Interrupt>.
```


----------------------------------------
Bug #12445: Testing TestIO#test_open_fifo_does_not_block_other_threads results in deadlock on cygwin
https://bugs.ruby-lang.org/issues/12445#change-58975

* Author: Martin Drst
* Status: Open
* Priority: Normal
* Assignee: Nobuyoshi Nakada
* ruby -v: ruby 2.4.0dev (2016-05-31 trunk 55228) [x86_64-cygwin]
* Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN
----------------------------------------
When I run `bin/ruby test/runner.rb test/ruby/test_*`, testing stops at `TestIO#test_open_fifo_does_not_block_other_threads`. Checking the task manager shows that this is a deadlock (there are two ruby interpreters running, but they don't use any CPU at all).

This is what I see for ages:

```
[1589/4545] TestIO#test_open_fifo_does_not_block_other_threads
```



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>