ruby.git/spec/ruby/library/conditionvariable/wait_spec.rb, branch v3_0_3

Refined "Drop support for ruby 2.4 from ruby/spec"

2020-04-03T00:44:40+00:00

By using spec/mspec/tool/remove_old_guards.rb.

[ruby/spec] Don't care about return values

2020-02-06T06:42:36+00:00

RDoc says nothing about them.  Added an example that
ConditionVariable#wait can be woken up by
ConditionVariable#signal, instead.

[ruby/spec] Check by Thread#stop?

2020-02-06T05:50:32+00:00

Check if threads are stopped by Thread#stop? instead of the status
name.

Update to ruby/spec@d419e74

2019-12-27T15:46:08+00:00

Update to ruby/spec@15c9619

2019-04-27T16:53:23+00:00

Update to ruby/spec@241f9e7

2018-09-25T10:41:16+00:00

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64831 b2dd03c8-39d4-4d8f-98ff-823fe69b080e

Revert r64471

2018-08-20T15:41:00+00:00

* This reverts commit 9ab04897bd06767f773b35c6958a0551981093aa:
  "don't run specs add at r64409 on Windows"
* It doesn't seem to help:
  http://mswinci.japaneast.cloudapp.azure.com/vc12-x64/ruby-trunk/recent.html

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64482 b2dd03c8-39d4-4d8f-98ff-823fe69b080e

don't run specs add at r64409 on Windows

2018-08-19T13:25:11+00:00

Maybe it breaks http://mswinci.japaneast.cloudapp.azure.com/vc12-x64/ruby-trunk/log/20180817T095734Z.fail.html.gz

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64471 b2dd03c8-39d4-4d8f-98ff-823fe69b080e

Revert r64441

2018-08-18T13:52:53+00:00

* This reverts commit 647fc1227a4146ecbfeb0d59358abc8d99cd8ae6:
  "thread_sync.c (rb_mutex_synchronize): only unlock if we own the mutex"
* Let's try to preserve the semantics of always being locked inside
  Mutex#synchronize, even if an exception interrupts ConditionVariable#wait.
* As discussed on [Bug #14999].

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64448 b2dd03c8-39d4-4d8f-98ff-823fe69b080e

thread_sync.c (rb_mutex_synchronize): only unlock if we own the mutex

2018-08-18T06:33:49+00:00

If an exception is raised inside Mutex#sleep (via ConditionVariable#wait),
we cannot guarantee we can own the mutex in the ensure callback.

However, who owns the mutex at that point does not matter.  What
matters is the Mutex is usable after an exception occurs.

* thread_sync.c (rb_mutex_synchronize): only unlock if we own the mutex

* spec/ruby/library/conditionvariable/wait_spec.rb: only test lock
  usability after thread kill.  Who owns the lock at any
  particular moment is an implementation detail which we cannot
  easily guarantee.

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64441 b2dd03c8-39d4-4d8f-98ff-823fe69b080e