ruby.git/test/fiber/test_mutex.rb, branch v3_2_11

mutex: Raise a ThreadError when detecting a fiber deadlock (#6680)

2022-11-08T11:43:16+00:00

[Bug #19105]

If no fiber scheduler is registered and the fiber that
owns the lock and the one that try to acquire it
both belong to the same thread, we're in a deadlock case.

Co-authored-by: Jean Boussier

Prefer qualified names under Thread

2021-06-29T02:41:10+00:00

Fix TestFiberMutex#test_condition_variable assertion

2020-11-08T15:49:33+00:00

* Now that it works correctly.

Rename to `Fiber#set_scheduler`.

2020-11-07T10:39:50+00:00

Refined assertions for better failure messages

2020-10-01T04:48:15+00:00

Remove `Thread.scheduler` from public interface.

2020-10-01T03:56:05+00:00

It's implementation is equivalent to:

Thread.current.scheduler unless Thread.current.blocking?

Remove from waiter in Mutex#lock with ensure when calling rb_scheduler_block()

2020-09-20T11:35:39+00:00

* Previously this could lead to an invalid waiter entry and then trying
  to wake up that waiter would result in various issues in rb_mutex_unlock_th().

Fix Mutex#unlock with a scheduler and thread contention

2020-09-17T13:15:43+00:00

* It would hit "[BUG] unexpected THREAD_STOPPED" before.

Call scheduler.block instead of scheduler.kernel_sleep for blocking Queue/SizedQueue operations

2020-09-17T12:59:38+00:00

* scheduler.unblock was already already called before but with no corresponding scheduler.block
* add test that Queue#pop makes the scheduler wait until it gets an element.

Add support for Queue & SizedQueue.

2020-09-14T04:44:09+00:00