* [ruby-core:94419] [Ruby master Bug#16110] Doesn't detect deadlock on Ruby 2.4 and 2.5 on Windows
[not found] <redmine.issue-16110.20190818200912@ruby-lang.org>
@ 2019-08-18 20:09 ` josh.cheek
2019-08-19 14:28 ` [ruby-core:94435] " Greg.mpls
1 sibling, 0 replies; 2+ messages in thread
From: josh.cheek @ 2019-08-18 20:09 UTC (permalink / raw)
To: ruby-core
Issue #16110 has been reported by josh.cheek (Josh Cheek).
----------------------------------------
Bug #16110: Doesn't detect deadlock on Ruby 2.4 and 2.5 on Windows
https://bugs.ruby-lang.org/issues/16110
* Author: josh.cheek (Josh Cheek)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: ruby 2.5.5p157 (2019-03-15 revision 67260) [i386-mingw32]
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
The following code is detected as a deadlock, except in Ruby 2.4 and 2.5 on Windows:
``` sh
ruby -r thread -ve 'Thread.new { Queue.new.shift }.join'
```
You can see it run in this code: https://github.com/JoshCheek/childprocess_experiment/blob/368052de8e433933035395216e8c48b8302b6fdf/Rakefile#L3
And it gets stuck in AppVeyor's CI because it doesn't realize it's deadlocked: https://ci.appveyor.com/project/JoshCheek/childprocess-experiment/build/job/3j06xan4ygm63ppd
--
https://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] 2+ messages in thread
* [ruby-core:94435] [Ruby master Bug#16110] Doesn't detect deadlock on Ruby 2.4 and 2.5 on Windows
[not found] <redmine.issue-16110.20190818200912@ruby-lang.org>
2019-08-18 20:09 ` [ruby-core:94419] [Ruby master Bug#16110] Doesn't detect deadlock on Ruby 2.4 and 2.5 on Windows josh.cheek
@ 2019-08-19 14:28 ` Greg.mpls
1 sibling, 0 replies; 2+ messages in thread
From: Greg.mpls @ 2019-08-19 14:28 UTC (permalink / raw)
To: ruby-core
Issue #16110 has been updated by MSP-Greg (Greg L).
Is this specific to 32 bit builds of 2.4 & 2.5? I think 64 bit builds all function as expected...
----------------------------------------
Bug #16110: Doesn't detect deadlock on Ruby 2.4 and 2.5 on Windows
https://bugs.ruby-lang.org/issues/16110#change-80860
* Author: josh.cheek (Josh Cheek)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: ruby 2.5.5p157 (2019-03-15 revision 67260) [i386-mingw32]
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
The following code is detected as a deadlock, except in Ruby 2.4 and 2.5 on Windows:
``` sh
ruby -r thread -ve 'Thread.new { Queue.new.shift }.join'
```
You can see it run in this code: https://github.com/JoshCheek/childprocess_experiment/blob/368052de8e433933035395216e8c48b8302b6fdf/Rakefile#L3
And it gets stuck in AppVeyor's CI because it doesn't realize it's deadlocked: https://ci.appveyor.com/project/JoshCheek/childprocess-experiment/build/job/3j06xan4ygm63ppd
--
https://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-08-19 14:28 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <redmine.issue-16110.20190818200912@ruby-lang.org>
2019-08-18 20:09 ` [ruby-core:94419] [Ruby master Bug#16110] Doesn't detect deadlock on Ruby 2.4 and 2.5 on Windows josh.cheek
2019-08-19 14:28 ` [ruby-core:94435] " Greg.mpls
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).