GitHub user JoshRosen opened a pull request:

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

    [SPARK-11647][WIP] Attempt to reduce time/flakiness of Thriftserver CLI and 
SparkSubmit tests

    This work-in-progress patch aims to reduce the test time and flakiness of 
HiveSparkSubmitSuite, SparkSubmitSuite, and CliSuite.
    
    Key changes:
    
    - Disable IO synchronization calls for Derby writes, since durability 
doesn't matter for tests. This was done for HiveCompatibilitySuite in #6651 and 
resulted in huge test speedups.
    - Add a few missing `--conf`s to disable various Spark UIs. The CliSuite, 
in particular, never disabled these UIs, leaving it prone to 
port-contention-related flakiness.
    - Fix two instances where tests defined `beforeAll()` methods which were 
never called because the appropriate traits were not mixed in. I updated these 
tests suites to extend `BeforeAndAfterEach` so that they play nicely with our 
`ResetSystemProperties` trait.

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

    $ git pull https://github.com/JoshRosen/spark SPARK-11647

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

    https://github.com/apache/spark/pull/9623.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 #9623
    
----
commit 801afe7d1b0666c3f84c1e030ede72d0dc35300c
Author: Josh Rosen <[email protected]>
Date:   2015-11-11T07:31:16Z

    Misc. test conf changes aimed at reducing test time / flakiness.

----


---
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