GitHub user zsxwing opened a pull request:

    https://github.com/apache/spark/pull/17597

    [SPARK-20285][Tests]Increase the pyspark streaming test timeout to 30 
seconds

    ## What changes were proposed in this pull request?
    
    Saw the following failure locally:
    
    ```
    Traceback (most recent call last):
      File "/home/jenkins/workspace/python/pyspark/streaming/tests.py", line 
351, in test_cogroup
        self._test_func(input, func, expected, sort=True, input2=input2)
      File "/home/jenkins/workspace/python/pyspark/streaming/tests.py", line 
162, in _test_func
        self.assertEqual(expected, result)
    AssertionError: Lists differ: [[(1, ([1], [2])), (2, ([1], [... != []
    
    First list contains 3 additional elements.
    First extra element 0:
    [(1, ([1], [2])), (2, ([1], [])), (3, ([1], []))]
    
    + []
    - [[(1, ([1], [2])), (2, ([1], [])), (3, ([1], []))],
    -  [(1, ([1, 1, 1], [])), (2, ([1], [])), (4, ([], [1]))],
    -  [('', ([1, 1], [1, 2])), ('a', ([1, 1], [1, 1])), ('b', ([1], [1]))]]
    ```
    
    It also happened on Jenkins: 
http://spark-tests.appspot.com/builds/spark-branch-2.1-test-sbt-hadoop-2.7/120
    
    It's because when the machine is overloaded, the timeout is not enough. 
This PR just increases the timeout to 30 seconds.
    
    ## How was this patch tested?
    
    Jenkins

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/zsxwing/spark SPARK-20285

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/17597.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #17597
    
----
commit 67a12213b8abbb9c41333ff9e0ffb3f70944a12e
Author: Shixiong Zhu <shixi...@databricks.com>
Date:   2017-04-10T19:47:21Z

    Increase the pyspark streaming test timeout to 30 seconds

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to