You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Wenchen Fan (JIRA)" <ji...@apache.org> on 2019/04/18 12:57:00 UTC
[jira] [Resolved] (SPARK-27460) Running slowest test suites in
their own forked JVMs for higher parallelism
[ https://issues.apache.org/jira/browse/SPARK-27460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wenchen Fan resolved SPARK-27460.
---------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
Issue resolved by pull request 24373
[https://github.com/apache/spark/pull/24373]
> Running slowest test suites in their own forked JVMs for higher parallelism
> ---------------------------------------------------------------------------
>
> Key: SPARK-27460
> URL: https://issues.apache.org/jira/browse/SPARK-27460
> Project: Spark
> Issue Type: Improvement
> Components: Tests
> Affects Versions: 3.0.0
> Reporter: Xiao Li
> Assignee: Gengliang Wang
> Priority: Critical
> Fix For: 3.0.0
>
>
> We should modify SparkBuild so that the largest / slowest test suites (or collections of suites) can run in their own forked JVMs, allowing them to be run in parallel with each other
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org