-
Notifications
You must be signed in to change notification settings - Fork 28.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SPARK-11672] [ML] flaky spark.ml read/write tests #9677
Conversation
test this please |
1 similar comment
test this please |
Test build #45770 has finished for PR 9677 at commit
|
Test build #45773 has finished for PR 9677 at commit
|
Okay, I think the problem is |
|
Test build #45790 has finished for PR 9677 at commit
|
Test build #45788 has finished for PR 9677 at commit
|
LGTM |
Merged into master and branch-1.6. |
We set `sqlContext = null` in `afterAll`. However, this doesn't change `SQLContext.activeContext` and then `SQLContext.getOrCreate` might use the `SparkContext` from previous test suite and hence causes the error. This PR calls `clearActive` in `beforeAll` and `afterAll` to avoid using an old context from other test suites. cc: yhuai Author: Xiangrui Meng <meng@databricks.com> Closes #9677 from mengxr/SPARK-11672.2. (cherry picked from commit e71c075) Signed-off-by: Xiangrui Meng <meng@databricks.com>
We set `sqlContext = null` in `afterAll`. However, this doesn't change `SQLContext.activeContext` and then `SQLContext.getOrCreate` might use the `SparkContext` from previous test suite and hence causes the error. This PR calls `clearActive` in `beforeAll` and `afterAll` to avoid using an old context from other test suites. cc: yhuai Author: Xiangrui Meng <meng@databricks.com> Closes apache#9677 from mengxr/SPARK-11672.2.
@mengxr I just saw a failure that seems related to this PR at https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45914/consoleFull
|
We set
sqlContext = null
inafterAll
. However, this doesn't changeSQLContext.activeContext
and thenSQLContext.getOrCreate
might use theSparkContext
from previous test suite and hence causes the error. This PR callsclearActive
inbeforeAll
andafterAll
to avoid using an old context from other test suites.cc: @yhuai