From 2b5647665a431daebbf35a80f3e9ed74f95d1296 Mon Sep 17 00:00:00 2001
From: Andrii Rosa <andriirosa@fb.com>
Date: Thu, 13 Feb 2020 10:33:18 -0500
Subject: [PATCH] Run presto spark tests in forked VM

The tests no longer use stream redirects thus the workaround is
no longer needed.
---
 presto-spark-testing/pom.xml | 10 ----------
 1 file changed, 10 deletions(-)

diff --git a/presto-spark-testing/pom.xml b/presto-spark-testing/pom.xml
index 7f8acb1200508..7558f066b6d24 100644
--- a/presto-spark-testing/pom.xml
+++ b/presto-spark-testing/pom.xml
@@ -122,16 +122,6 @@
                     </ignoredResourcePatterns>
                 </configuration>
             </plugin>
-
-            <!-- Workaround for "Corrupted STDOUT by directly writing to native stream in forked JVM 1" -->
-            <!-- https://stackoverflow.com/questions/55632614/maven-surefire-plugin-crahsing-jvm-on-java-11-corrupted-stdout-by-directly-writ -->
-            <plugin>
-                <groupId>org.apache.maven.plugins</groupId>
-                <artifactId>maven-surefire-plugin</artifactId>
-                <configuration>
-                    <forkCount>0</forkCount>
-                </configuration>
-            </plugin>
         </plugins>
     </build>
 </project>