ruby.git/tool/lib/test, branch v3_2_11 The Ruby Programming Language Use class methods of `File` over `Kernel.open` and `IO.read` 2022-11-30T17:28:49+00:00 Nobuyoshi Nakada nobu@ruby-lang.org 2022-11-25T05:22:37+00:00 d752cf7601adbe4bc2dc658effc2f61563a7dfb7 






jobserver option may not be at the last
2022-11-07T01:08:09+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2022-11-07T00:43:45+00:00

ab01b8f23f1e218fa5a360806120a1d6eaaa228f












Set `autoclose:` for inherited FDs only [ci skip]
2022-11-07T00:06:15+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2022-11-07T00:06:15+00:00

180d37c817dc55f27b7f4ea1278a36a691491148












GNU make 4.4 now uses a fifo for the jobserver
2022-11-06T14:39:55+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2022-11-06T14:39:55+00:00

12883f8fa6222324880e2b0f161f8c6d6cf365c7












Fix crash in test runner on timeout
2022-11-02T17:34:02+00:00

Peter Zhu
peter@peterzhu.ca

2022-11-02T17:34:02+00:00

b777408c33b57077f8be09eaed9245eeca0b59c5

When a test worker hangs and timeouts, the test runner crashes with the
following stack trace:

ruby/tool/lib/test/unit.rb:1747:in `puke': undefined method `backtrace' for Timeout::Error:Class (NoMethodError)
	from ruby/tool/lib/test/unit.rb:790:in `block in _run_parallel'
	from ruby/tool/lib/test/unit.rb:788:in `each'

This commit adds handling for Timeout::Error and outputs a message.





When a test worker hangs and timeouts, the test runner crashes with the
following stack trace:

ruby/tool/lib/test/unit.rb:1747:in `puke': undefined method `backtrace' for Timeout::Error:Class (NoMethodError)
	from ruby/tool/lib/test/unit.rb:790:in `block in _run_parallel'
	from ruby/tool/lib/test/unit.rb:788:in `each'

This commit adds handling for Timeout::Error and outputs a message.







Enable deprecation warnings for test-all
2022-09-10T11:14:18+00:00

Benoit Daloze
eregontp@gmail.com

2022-09-03T13:47:49+00:00

92b907d12d6de6f74f1efa6d8cd4fed8fa50763e

* So deprecated methods/constants/functions are dealt with early,
  instead of many tests breaking suddenly when removing a deprecated
  method/constant/function.
* Follows https://bugs.ruby-lang.org/issues/17591





* So deprecated methods/constants/functions are dealt with early,
  instead of many tests breaking suddenly when removing a deprecated
  method/constant/function.
* Follows https://bugs.ruby-lang.org/issues/17591







Add `--stdout-on-failure`, the reverse of `--stderr-on-failure`
2022-07-05T05:40:19+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2022-07-05T00:37:17+00:00

5921bfc7ce91aa8079dd8ac4faf873ec911ce320












Separate failed output option
2022-07-05T05:40:19+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2022-07-05T00:31:32+00:00

1b34bd07c18068228188a72f94662cceac50f30e

It is unrelated to `GlobOption` at all.





It is unrelated to `GlobOption` at all.







Prevent accidental use of assert_raises
2022-06-25T10:09:06+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2022-06-25T10:05:36+00:00

f159bbd17da88a7f456e0ec7fbf7890135d456a3












Rename test_jit to test_mjit
2022-05-21T04:32:55+00:00

Takashi Kokubun
takashikkbn@gmail.com

2022-05-21T04:31:00+00:00

ead96e7b44b98bef4896d836239345012821f1d2

to avoid confusion with YJIT





to avoid confusion with YJIT