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

Posted to issues@phoenix.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2023/05/06 19:05:00 UTC

[jira] [Commented] (PHOENIX-6945) Update 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:comment-tabpanel&focusedCommentId=17720246#comment-17720246 ] 

ASF GitHub Bot commented on PHOENIX-6945:
-----------------------------------------

stoty closed pull request #1600: PHOENIX-6945 Update to Surefire plugin to 3.0.0 and switch to TCP for…
URL: https://github.com/apache/phoenix/pull/1600




> Update 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)