RubySpec: Thread#stop? reports aborting on a killed thread FAILED
-----------------------------------------------------------------
Key: JRUBY-3587
URL: http://jira.codehaus.org/browse/JRUBY-3587
Project: JRuby
Issue Type: Bug
Components: Core Classes/Modules
Affects Versions: JRuby 1.2
Reporter: Charles Oliver Nutter
This is a result of our moving critical= to be a global mutex instead of a
stop-the-world. The following code from thread/fixtures/classes.rb expects that
the killed thread won't start running again until critical has been released:
{noformat}
def self.status_of_aborting_thread
t = Thread.new { sleep }
begin
Thread.critical = true
t.kill
Status.new t
ensure
Thread.critical = false
end
end
{noformat}
Because in JRuby, critical only prevents two threads from criticalizing at the
same time (rather than critical preventing any threads from running other than
the current), this fails sporadically.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
