You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by GitBox <gi...@apache.org> on 2022/01/22 13:20:52 UTC

[GitHub] [maven-surefire] Tibor17 edited a comment on pull request #299: [SUREFIRE-1629] Added integration test for surefire-1629

Tibor17 edited a comment on pull request #299:
URL: https://github.com/apache/maven-surefire/pull/299#issuecomment-1019244699


   @cowwoc 
   We have several integration tests which are using `<forkNode implementation="org.apache.maven.plugin.surefire.extensions.SurefireForkNodeFactory"/>`. For instance see the tests in `ConsoleOutputIT`. Truly it is hard to simulate native calls with standard output, for instance JVM and GC of JPMS uses native calls in order to print the JVM warning (regarding JVM warnings `Error occurred during initialization of boot layer`) on the standard output and error. One way would be `java.io.FileDescriptor.out` obviosly refers to the native calls, but I do not use to show it in the public audience. If you would try to use native calls in new integration test, then it would confirm the fix with `<forkNode implementation="org.apache.maven.plugin.surefire.extensions.SurefireForkNodeFactory"/>`.


-- 
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: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org