ruby.git/test/ruby/test_process.rb, branch v3_3_11 The Ruby Programming Language Add predicates for platforms 2025-12-15T08:38:38+00:00 Nobuyoshi Nakada nobu@ruby-lang.org 2024-09-10T06:37:32+00:00 3563a0db80566b7c22ca77e620a9e89bb928dba2 






Pend some tests because these are not working with macOS 15 beta and Xcode 16 beta
2025-12-15T08:38:38+00:00

Hiroshi SHIBATA
hsbt@ruby-lang.org

2024-07-12T03:35:58+00:00

c98aa9771ed09ba209aba17b341a893f6c1594d4












merge revision(s) 8034e9c3d001ca3dff124ab42972684eac8af2ae: [Backport #20995]
2025-01-15T01:59:12+00:00

Takashi Kokubun
takashikkbn@gmail.com

2025-01-15T01:59:12+00:00

12a0807965624a0be37dc79371a69b5d787cc8d1

	[Bug #20995] Protect `IO.popen` block from exiting by exception





	[Bug #20995] Protect `IO.popen` block from exiting by exception







merge revision(s) a7ff264477105b5dc0ade6facad4176a1b73df0b: [Backport #20393]
2024-05-29T18:46:33+00:00

Takashi Kokubun
takashikkbn@gmail.com

2024-05-29T18:46:33+00:00

6e46a363a8f29d93cf6992805ee67d029cea030f

	Don't clear pending interrupts in the parent process. (#10365)





	Don't clear pending interrupts in the parent process. (#10365)







Change test_warmup_frees_pages to check each size pool
2024-05-29T16:40:45+00:00

Peter Zhu
peter@peterzhu.ca

2023-12-30T03:14:38+00:00

3cab9b997945ba5d3d06b374d5e12e07293f8e73

This should help in debugging the intermittent test failures on CI:

    TestProcess#test_warmup_frees_pages [test/ruby/test_process.rb:2779]:
    <201> expected but was
    <202>.





This should help in debugging the intermittent test failures on CI:

    TestProcess#test_warmup_frees_pages [test/ruby/test_process.rb:2779]:
    <201> expected but was
    <202>.







String#force_encoding don't clear coderange if encoding is unchanged
2023-11-09T11:38:10+00:00

Jean Boussier
byroot@ruby-lang.org

2023-11-08T13:05:52+00:00

ea1b1ea1aa98bc9488564ef18aa4032aa1cb5536

Some code out there blind calls `force_encoding` without checking
what the original encoding was, which clears the coderange uselessly.

If the String is big, it can be a rather costly mistake.

For instance the `rack-utf8_sanitizer` gem does this on request
bodies.





Some code out there blind calls `force_encoding` without checking
what the original encoding was, which clears the coderange uselessly.

If the String is big, it can be a rather costly mistake.

For instance the `rack-utf8_sanitizer` gem does this on request
bodies.







Revert "Add debug info for flaky test_warmup_frees_pages"
2023-10-27T18:28:56+00:00

Peter Zhu
peter@peterzhu.ca

2023-10-27T18:28:56+00:00

d654d580f388a1ffc60e74d4b05f753c884ec543

This reverts commit db3b814cb0ff6ffe83fe0c4f66cd6ce8951c3ca7.

This debugging information is no longer needed.





This reverts commit db3b814cb0ff6ffe83fe0c4f66cd6ce8951c3ca7.

This debugging information is no longer needed.







Magical wait to get rid of deadlock on macOS
2023-09-22T14:45:54+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2023-09-22T14:43:28+00:00

ea5f8e123cb04f995ffd1f893a22e45d5693a8ea












[Bug #19868] Deprecate `Process::Status#&` and `Process::Status#>>`
2023-09-14T06:26:25+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2023-09-14T06:19:15+00:00

998ae7c3f36b65f04471cd680b4c7ac78b3d9f30












[Bug #19868] Suggest other Process::Status method for `&` and `>>`
2023-09-14T05:57:57+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2023-09-07T02:47:43+00:00

b6de0a6c69a4857ca4347f65d7c9a5cb6e52c5bd

`Process::Status#&` and `Process::Status#>>` are provided only for
the backward compatibility with older Ruby than 1.8 where `$?` was
a `Fixnum`, and the knowledge about internals of system dependent
macros is necessary to use them.  Modern programs and libraries
should not need these methods.





`Process::Status#&` and `Process::Status#>>` are provided only for
the backward compatibility with older Ruby than 1.8 where `$?` was
a `Fixnum`, and the knowledge about internals of system dependent
macros is necessary to use them.  Modern programs and libraries
should not need these methods.