Backport #1484
closedRuby 1.8.6_p368 and Ruby 1.8.7_p160 have threading regressions
Description
=begin
Changes introduced in ruby 1.8.6_368 and ruby 1.8.7_p160 have regressions in the way they handle threading.
The following bug report for Capistrano details the regression: https://capistrano.lighthouseapp.com/projects/8716/tickets/79-capistrano-hangs-on-shell-command-for-many-computers-on-ruby-186-p368#ticket-79-22
Basically, when trying to deploy to more than one machine capistrano now hangs while eating up all CPU, instead of actually running the deployment tasks. Deploying to a single machine or deploying with e.g. ruby 1.8.7_p72 works fine.
=end
Updated by rogerdpack (Roger Pack) almost 15 years ago
=begin
Basically, when trying to deploy to more than one machine capistrano now hangs while eating up all CPU, instead of actually running the deployment tasks. Deploying to a single machine or deploying with e.g. ruby 1.8.7_p72 works fine.
Is this still the case?
=r
=end
Updated by luislavena (Luis Lavena) almost 15 years ago
=begin
On Wed, Jul 8, 2009 at 5:24 PM, Roger Packredmine@ruby-lang.org wrote:
Issue #1484 has been updated by Roger Pack.
Basically, when trying to deploy to more than one machine capistrano now hangs while eating up all CPU, instead of actually running the deployment tasks. Deploying to a single machine or deploying with e.g. ruby 1.8.7_p72 works fine.
Is this still the case?
=r
I see similar problems with all threading related tasks on Mongrel and
sqlite3-ruby threaded tests.
Could be a duplicate of the other bug report.¶
Luis Lavena
AREA 17
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exupéry
=end
Updated by hansdegraaff (Hans de Graaff) almost 15 years ago
=begin
http://redmine.ruby-lang.org/issues/show/1471 contains some discussion and patches that I thought were successfull, but it seems in my initial testing I was lucky or not careful enough. In any case I'm still seeing this problem with capistrano deployments when deploying to more than one machine at the time.
=end
Updated by dazuma (Daniel Azuma) over 14 years ago
=begin
I just reported http://redmine.ruby-lang.org/issues/show/1993 against 1.8.7, which looks like it's the same issue. (Sorry, I should have looked through the bug lists of the other versions-- I had thought this was 1.8.7 specific.) That other report has some analysis of rb_thread_schedule() that I think explains why this is happening. See also http://www.daniel-azuma.com/blog/view/z2ysbx0e4c3it9/ruby_1_8_7_io_select_threading_bug
=end
Updated by hongli (Hongli Lai) over 14 years ago
=begin
Hi guys, any updates on this ticket? Has it been fixed yet?
=end
Updated by hansdegraaff (Hans de Graaff) over 14 years ago
=begin
As far as I know this has not been fixed yet, but net-ssh-2.0.14 contains a workaround that works with capistrano.
=end
Updated by jeremyevans0 (Jeremy Evans) almost 5 years ago
- Tracker changed from Bug to Backport
- Project changed from Ruby 1.8 to Backport187
- Description updated (diff)
- Status changed from Open to Closed
- ruby -v deleted (
1.8.6_p368, ruby 1.8.7_p160)