Skip to content
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.

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

[WFCORE-6454] Use TCP/IP process communication for surefire plugin #5605

Merged
merged 1 commit into from
Aug 16, 2023

Commits on Aug 14, 2023

  1. [WFCORE-6454] Use TCP/IP process communication for surefire plugin

    This change utilizes new TCP/IP communication for surefire execution
    [1].
    
    By default, the communication writes to STDOUT which may lead to similar
    messages in the execution output if something else also writes there at
    wrong time:
    
    ```
    [WARNING] Corrupted STDOUT by directly writing to native stream in forked JVM 1.
    See FAQ web page and the dump file ... .dumpstream.
    ```
    
    This change should mittigate such warnings and also should reduce number
    of open files during execution which may lead to crash on some systems
    with `nofile` limit set quite low.
    
    Truth is that this issue hasn't been seen in this upstream WildFly Core
    project, still I believe this change should be beneficial avoiding
    eventual issue in the future.
    
    [1] https://maven.apache.org/surefire/maven-surefire-plugin/examples/process-communication.html
    jstourac committed Aug 14, 2023
    Configuration menu
    Copy the full SHA
    771d02d View commit details
    Browse the repository at this point in the history