ruby.git/test/.excludes, branch v4.0.2

Handle deeply nested capture variables syntax err

2025-11-17T02:30:24+00:00

When there are nested capture variables inside of a pattern match
that has an alternation pattern, it is a syntax error. Currently it
only adds a syntax error when it is at the top level of the pattern.

Exclude `JSON::GenericObject` test

2025-09-13T10:29:05+00:00

It depends on ostruct gem that is no longer a part of the default
gems, and the all tests are just skipped with a warning.

Skip `URI::TestMailTo#test_email_regexp` for now

2025-07-15T07:52:03+00:00

Remove test/.excludes/_appveyor

2025-07-07T23:32:35+00:00

We don't run AppVeyor anymore, so we shouldn't need this.

Do not intern invalid symbols in eval parse

2025-01-08T03:30:16+00:00

When the inner code cannot represent the name of the locals in the
outer code, do not bother putting them into the constant pool as
they will not be referenced.

Fixes [Bug #20992]

Co-authored-by: Nobuyoshi Nakada

[Bug #20992] Test for local variable name encodings

2024-12-30T08:04:09+00:00

Use wide character startup

2024-11-05T14:04:49+00:00

Mingw crt-git 12.0.0.r369.g0d4221712-1 now prohibits "command line
contains characters that are not supported in the active code page".
https://sourceforge.net/p/mingw-w64/mingw-w64/ci/0d42217123d3aec0341b79f6d959c76e09648a1e/

Already Ruby builds `argv` in `rb_w32_sysinit`, instead of mswin- or
mingw-made `argv`.  Just bypass the conversion in mingw crt.

Mingw: Exclude failing tests due to the crt change

2024-11-04T12:12:49+00:00

Mingw crt-git 12.0.0.r369.g0d4221712-1 now prohibits "command line
contains characters that are not supported in the active code page".
https://sourceforge.net/p/mingw-w64/mingw-w64/ci/0d42217123d3aec0341b79f6d959c76e09648a1e/

Provisionally exclude tests that fail by passing such characters.

M:N thread scheduler for Ractors

2023-10-12T05:47:01+00:00

This patch introduce M:N thread scheduler for Ractor system.

In general, M:N thread scheduler employs N native threads (OS threads)
to manage M user-level threads (Ruby threads in this case).
On the Ruby interpreter, 1 native thread is provided for 1 Ractor
and all Ruby threads are managed by the native thread.

From Ruby 1.9, the interpreter uses 1:1 thread scheduler which means
1 Ruby thread has 1 native thread. M:N scheduler change this strategy.

Because of compatibility issue (and stableness issue of the implementation)
main Ractor doesn't use M:N scheduler on default. On the other words,
threads on the main Ractor will be managed with 1:1 thread scheduler.

There are additional settings by environment variables:

`RUBY_MN_THREADS=1` enables M:N thread scheduler on the main ractor.
Note that non-main ractors use the M:N scheduler without this
configuration. With this configuration, single ractor applications
run threads on M:1 thread scheduler (green threads, user-level threads).

`RUBY_MAX_CPU=n` specifies maximum number of native threads for
M:N scheduler (default: 8).

This patch will be reverted soon if non-easy issues are found.

[Bug #19842]

Prefix `excludes` with a dot to prevent chkbuild from firing wrongly

2023-08-13T06:23:54+00:00

Chkbuild runs for each directories just under `test` directory when
`test-all` failed.  `test/excludes` itself should not be a target.