GitHub user tone-zhang opened a pull request:

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

    [SPARK-17330] [SPARK UT] Fix the failure Spark UT (SPARK-8368) case

    ## What changes were proposed in this pull request?
    
    Check the database warehouse used in Spark UT, and remove the existing 
database file before run the UT (SPARK-8368).
    
    
    ## How was this patch tested?
    
    Run Spark UT with the command for several times:
    ./build/sbt -Pyarn -Phadoop-2.6 -Phive -Phive-thriftserver "test-only 
*HiveSparkSubmitSuit*"
    Without the patch, the test case can be passed only at the first time, and 
always failed from the second time. 
    With the patch the test case always can be passed correctly.


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

    $ git pull https://github.com/tone-zhang/spark issue1

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

    https://github.com/apache/spark/pull/14894.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 #14894
    
----
commit b85db0658012d3c1bc88a6adc76a6aac70cefdd3
Author: tone-zhang <[email protected]>
Date:   2016-08-31T10:21:20Z

        [SPARK-17330] Fix the failure Spark UT (SPARK-8368) case
    
    When run Spark UT based on the latest version of master branch,
    the UT case (SPARK-8368) can be passed at the first time, but
    always fail if run it again.
    The failure reason is the test database file has been existed
    before run the case.

----


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to