GitHub user HyukjinKwon reopened a pull request:

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

    [SPARK-24886][INFRA] Fix the testing script to increase timeout for Jenkins 
build (from 300m to 330m)

    ## What changes were proposed in this pull request?
    
    Currently, looks we hit the time limit time to time. Looks better 
increasing the time a bit.
    
    For instance, please see https://github.com/apache/spark/pull/21822
    
    For clarification, current Jenkins timeout is already 361m:
    
    ![screen shot 2018-07-23 at 1 28 57 
pm](https://user-images.githubusercontent.com/6477701/43058956-c0f94880-8e7c-11e8-86ba-20cdd92a1f14.png)
    
    This PR just proposes to fix the test script to increase it correspondingly.
    
    *This PR does not target to change the build configuration*
    
    ## How was this patch tested?
    
    Jenkins tests.

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

    $ git pull https://github.com/HyukjinKwon/spark SPARK-24886

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

    https://github.com/apache/spark/pull/21845.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 #21845
    
----
commit c57b74546b457d44e0c9d28d92a672fe5324d3ff
Author: hyukjinkwon <gurwls223@...>
Date:   2018-07-23T05:30:16Z

    Fix the testing script to increase timeout for Jenkins build (from 300m to 
350m)

commit 7afc5c52fa31595b1eb458100d37fe92f62e31aa
Author: hyukjinkwon <gurwls223@...>
Date:   2018-07-23T05:38:09Z

    Looks 330m good enough actually for now

----


---

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

Reply via email to