From: "nagachika (Tomoyuki Chikanaga)" <nagachika00@...>
Date: 2013-12-13T14:55:45+09:00
Subject: [ruby-core:59085] [ruby-trunk - Bug #9211][Third Party's Issue] Bug	in can_detect_signals? in test/rake/test_rake_functional.rb


Issue #9211 has been updated by nagachika (Tomoyuki Chikanaga).

Status changed from Open to Third Party's Issue

Hello,

Thank you for your report.
rake has upstream repository. Please report to there

https://github.com/jimweirich/rake

Thanks
----------------------------------------
Bug #9211: Bug in can_detect_signals? in test/rake/test_rake_functional.rb
https://bugs.ruby-lang.org/issues/9211#change-43637

Author: snaury (Alexey Borzenkov)
Status: Third Party's Issue
Priority: Normal
Assignee: 
Category: 
Target version: 
ruby -v: ruby 2.1.0dev (2013-12-04 trunk 43989) [x86_64-linux]
Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN


In function can_detect_signals? in file test/rake/test_rake_functional.rb ruby is spawned incorrectly. There should be multiple parameters in a system call, since otherwise ruby is spawned from a shell, status ends up in a shell, and shell is not killed with a signal (obviously). Currently this causes test_signal_propagation_in_tests to be skipped on Linux. Attached patch fixes the problem, test is no longer skipped and now passes on Linux.


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