You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Istvan Toth (Jira)" <ji...@apache.org> on 2023/05/04 05:48:00 UTC

[jira] [Updated] (PHOENIX-6945) Update to Surefire plugin to 3.0.0 and switch to TCP forkNode implementation

     [ https://issues.apache.org/jira/browse/PHOENIX-6945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Istvan Toth updated PHOENIX-6945:
---------------------------------
    Summary: Update to Surefire plugin to 3.0.0 and switch to TCP forkNode implementation  (was: Update to Surefire plugin to 3.0.0 and switch to TCP)

> Update to Surefire plugin to 3.0.0 and switch to TCP forkNode implementation
> ----------------------------------------------------------------------------
>
>                 Key: PHOENIX-6945
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6945
>             Project: Phoenix
>          Issue Type: Bug
>          Components: connectors, core, omid, queryserver
>            Reporter: Istvan Toth
>            Assignee: Istvan Toth
>            Priority: Major
>
> Surefire 3.0.0 has been released.
> It has the option of using a different proticol for communicating with the test executors, which may or may not fix some of the sporadical "[WARNING] Corrupted channel by directly writing to native stream in forked JVM" events we see.
> https://maven.apache.org/surefire/maven-surefire-plugin/examples/process-communication.html#the-tcp-ip-communication-channel



--
This message was sent by Atlassian Jira
(v8.20.10#820010)