You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Davies Liu (JIRA)" <ji...@apache.org> on 2015/06/30 06:33:04 UTC
[jira] [Resolved] (SPARK-5161) Parallelize Python test execution
[ https://issues.apache.org/jira/browse/SPARK-5161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davies Liu resolved SPARK-5161.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.5.0
Issue resolved by pull request 7031
[https://github.com/apache/spark/pull/7031]
> Parallelize Python test execution
> ---------------------------------
>
> Key: SPARK-5161
> URL: https://issues.apache.org/jira/browse/SPARK-5161
> Project: Spark
> Issue Type: Improvement
> Components: Project Infra
> Affects Versions: 1.2.0
> Reporter: Nicholas Chammas
> Assignee: Josh Rosen
> Fix For: 1.5.0
>
>
> [Original discussion here.|https://github.com/apache/spark/pull/3564#issuecomment-67785676]
> As of 1.2.0, Python tests take around 10-12 minutes to run. Once [SPARK-3431] is complete, this will become a significant fraction of the total test time.
> There are 2 separate approaches to explore for parallelizing the execution of Python unit tests:
> * Use GNU parallel to run each Python test file in parallel.
> * Use [{{nose}}|http://nose.readthedocs.org/en/latest/doc_tests/test_multiprocess/multiprocess.html] to parallelize all Python tests in a more extensible/configurable way.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org