Uh oh!
There was an error while loading. Please reload this page.
[SPARK-11672] [ML] flaky spark.ml read/write tests - #9677
Closed
mengxr wants to merge 4 commits into
Closed
Conversation
mengxr
commented
Nov 12, 2015
ContributorAuthor
test this please |
1 similar comment
mengxr
commented
Nov 12, 2015
ContributorAuthor
test this please |
SparkQA
commented
Nov 12, 2015
Test build #45770 has finished for PR 9677 at commit
|
SparkQA
commented
Nov 12, 2015
Test build #45773 has finished for PR 9677 at commit
|
mengxr
commented
Nov 12, 2015
ContributorAuthor
Okay, I think the problem is |
mengxr
commented
Nov 12, 2015
ContributorAuthor
|
SparkQA
commented
Nov 13, 2015
Test build #45790 has finished for PR 9677 at commit
|
SparkQA
commented
Nov 13, 2015
Test build #45788 has finished for PR 9677 at commit
|
yhuai
commented
Nov 13, 2015
Contributor
LGTM |
mengxr
commented
Nov 13, 2015
ContributorAuthor
Merged into master and branch-1.6. |
asfgit pushed a commit
that referenced
this pull request
Nov 13, 2015
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>
dskrvk pushed a commit
to dskrvk/spark
that referenced
this pull request
Nov 13, 2015
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> Closesapache#9677 from mengxr/SPARK-11672.2.
shivaram
commented
Nov 14, 2015
Contributor
@mengxr I just saw a failure that seems related to this PR at https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45914/consoleFull |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We set
sqlContext = nullinafterAll. However, this doesn't changeSQLContext.activeContextand thenSQLContext.getOrCreatemight use theSparkContextfrom previous test suite and hence causes the error. This PR callsclearActiveinbeforeAllandafterAllto avoid using an old context from other test suites.cc: @yhuai