ammachado opened a new pull request, #1720:
URL: https://github.com/apache/maven-mvnd/pull/1720

   ## Summary
   - `InputStreamNativeIT.installPluginAndCount` fails on CI (native GraalVM 
builds) because `NativeTestClient` spawns the real `mvnd` binary but never 
writes to or closes its stdin pipe.
   - The test's `RequestInput`/`RequestInputAvailable` message interception in 
`TestClientOutput` only works for the in-process JVM test client; for a native 
test the daemon talks to the spawned binary's own real OS-level stdin, which 
the harness never fed, so the mojo always saw 0 bytes available instead of the 
expected 10.
   - Adds `TestClientOutput.nativeStdin()` (defaults to `null`, so no behavior 
change for any other test) so a native IT can supply bytes that get written to 
the child process's real stdin and closed (EOF) before the daemon requests 
them, mirroring how a real `pipe | mvnd ...` invocation behaves.
   
   Confirmed on `apache/maven-mvnd`'s own `master` CI (e.g. run 30862194274, 
headSha `67d0a23d`) that this failure is pre-existing and unrelated to any 
particular feature branch — it reproduces identically on unmodified `master`.
   
   ## Test plan
   - [x] `./mvnw -pl dist -am install -DskipTests` then `./mvnw -pl 
integration-tests test -Dtest=InputStreamNativeIT` locally — compiles cleanly; 
fails only with "mvnd executable does not exist" since no GraalVM 
`native-image` toolchain is available in this environment (expected/inherent 
local limitation, not a code issue).
   - [x] `./mvnw -pl integration-tests test -Dtest=InputStreamTest` (JVM-mode 
counterpart) — passes, confirming the new `nativeStdin()` default is a no-op 
for the existing path.
   - [ ] CI (GraalVM native builds on ubuntu/macos/windows) to confirm 
`InputStreamNativeIT.installPluginAndCount` now passes.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to