GitHub user carsonwang opened a pull request: https://github.com/apache/spark/pull/9991
[SPARK-11206] (Followup) Fix SQLListenerMemoryLeakSuite test error A followup to #9297, fix the SQLListenerMemoryLeakSuite test error. The [failure](https://amplab.cs.berkeley.edu/jenkins/job/Spark-Master-Maven-pre-YARN/HADOOP_VERSION=2.0.0-mr1-cdh4.1.2,label=spark-test/4896/) occurs because a `sqlListener` created by a previous test suite is not cleared in the SQLListenerMemoryLeakSuite. In the failure case, the previous test suite DateFunctionsSuite has 91 completed executions. So the error message is `91 was not less than or equal to 50.` For test suites extends `SharedSQLContext`, the sqlListener is cleared in the method `beforeAll`. Since `SQLListenerMemoryLeakSuite` doesn't extends `SharedSQLContext`, the `sqlListener` need to be cleared manually before creating the `SQLContext`. /cc @vanzin @JoshRosen @chenghao-intel You can merge this pull request into a Git repository by running: $ git pull https://github.com/carsonwang/spark SQLListenerTestFix Alternatively you can review and apply these changes as the patch at: https://github.com/apache/spark/pull/9991.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 #9991 ---- commit 8ca3031948b56f5f54dced1b58de35ec27f1e370 Author: Carson Wang <carson.w...@intel.com> Date: 2015-11-26T06:41:10Z Fix SQLListenerMemoryLeakSuite test error ---- --- 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