[
https://issues.apache.org/jira/browse/SPARK-9487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15665370#comment-15665370
]
Saikat Kanjilal commented on SPARK-9487:
----------------------------------------
I am running the tests by the following command: ./build/mvn test -P...
-DwildcardSuites=none -Dtest=org.apache.spark.streaming.JavaAPISuite , is that
not the way Jenkins runs the tests , I noticed that locally I am getting the
same error as Jenkins shown here
(https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68529/consoleFull)
regardless of whether I set the configuration to local[2] or local[4]:
expected:<[[(hello,1), (world,1)], [(hello,1), (moon,1)], [(hello,1)]]> but
was:<[[(hello,1), (world,1)], [(moon,1), (hello,1)], [(hello,1)]]>
> Use the same num. worker threads in Scala/Python unit tests
> -----------------------------------------------------------
>
> Key: SPARK-9487
> URL: https://issues.apache.org/jira/browse/SPARK-9487
> Project: Spark
> Issue Type: Improvement
> Components: PySpark, Spark Core, SQL, Tests
> Affects Versions: 1.5.0
> Reporter: Xiangrui Meng
> Labels: starter
> Attachments: ContextCleanerSuiteResults, HeartbeatReceiverSuiteResults
>
>
> In Python we use `local[4]` for unit tests, while in Scala/Java we use
> `local[2]` and `local` for some unit tests in SQL, MLLib, and other
> components. If the operation depends on partition IDs, e.g., random number
> generator, this will lead to different result in Python and Scala/Java. It
> would be nice to use the same number in all unit tests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
