Skip to content

docs: clarify JRuby Windows support note #157

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jcouball merged 1 commit into from
Jan 4, 2026
Merged

docs: clarify JRuby Windows support note #157

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 5 additions & 10 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -203,17 +203,12 @@ This gem will be expected to function correctly on:
- The latest version of TruffleRuby 24+ on Linux

It is this project's intent to support the latest version of JRuby on Windows once
Process.wait2 and Process.wait work correctly on this platform.
Process.wait and Process.wait2 report subprocess status correctly on that platform
(tracking: https://github.com/main-branch/process_executer/issues/156).

Currently, JRuby on Windows does not capture and report the subprocess status via $?
(or $CHILD_STATUS), Process.wait, or Process.wait2. These values always return `nil`
for the status, preventing this gem from properly detecting command failures and
timeouts.

This repository includes a separate test suite in the `process_spawn_test/` directory
that specifically validates JRuby's subprocess behavior. The [Process Spawn Test
workflow](https://github.com/main-branch/process_executer/actions/workflows/process-spawn-test.yml)
can be run manually to verify the status of this issue.
This repository includes a separate test suite in the `process_spawn_test/` directory.
The [Process Spawn Test workflow](https://github.com/main-branch/process_executer/actions/workflows/process-spawn-test.yml)
can be run manually to check the current JRuby/Windows status.

## Breaking Changes

Expand Down