ruby.git/test/fiber/test_scheduler.rb, branch v3_4_9

Push a real iseq in rb_vm_push_frame_fname()

2025-03-14T19:04:25+00:00

Previously, vm_make_env_each() (used during proc
creation and for the debug inspector C API) picked up the
non-GC-allocated iseq that rb_vm_push_frame_fname() creates,
which led to a SEGV when the GC tried to mark the non GC object.

Put a real iseq imemo instead. Speed should be about the same since
the old code also did a imemo allocation and a malloc allocation.

Real iseq allows ironing out the special-casing of dummy frames in
rb_execution_context_mark() and rb_execution_context_update(). A check
is added to RubyVM::ISeq#eval, though, to stop attempts to run dummy
iseqs.

[Bug #21180]

Co-authored-by: Aaron Patterson

Ensure fiber scheduler re-acquires mutex when interrupted from sleep. (#12158)

2024-11-23T23:54:12+00:00

[Bug #20907]

Reduce number of iterations in `TestFiberScheduler#test_autoload`. (#8391)

2023-09-07T01:53:51+00:00

`ppc64le` appears to be struggling with this test due to timeout. Let's see
if reducing the number of iterations can help improve the test performance.

Wait killed threads

2022-12-02T14:46:21+00:00

Avoid missed wakeup with fiber scheduler and Fiber.blocking. (#6588)

2022-10-20T00:38:52+00:00

* Ensure that blocked fibers don't prevent valid wakeups.

Add missing `f.resume` to fiber test. (#6539)

2022-10-13T06:04:06+00:00

Introduce `Fiber.blocking{}` for bypassing the fiber scheduler. (#6498)

2022-10-06T10:00:49+00:00

Retain reference to blocking fibers.

2022-05-25T03:24:24+00:00

test/fiber/test_scheduler.rb: Remove the test file from $LOADED_FEATURES

2022-05-09T01:20:25+00:00

to prevent the following failure on `make test-all --repeat-count=2`

http://ci.rvm.jp/results/trunk-repeat20-asserts@phosphorus-docker/3957774
```
  1) Error:
TestFiberScheduler#test_autoload:
NameError: uninitialized constant TestFiberSchedulerAutoload
          Object.const_get(:TestFiberSchedulerAutoload)
                ^^^^^^^^^^
```

Use a proper mutex for autoloading features. (#5788)

2022-05-07T22:22:58+00:00

Object#autoload implements a custom per-thread "mutex" for blocking
threads waiting on autoloading a feature. This causes problems when used
with the fiber scheduler. We swap the implementation to use a Ruby mutex
which is fiber aware.