Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17905
Merged build finished. Test FAILed.
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17905
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76634/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17905
**[Test build #76634 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76634/testReport)**
for PR 17905 at commit
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/17905
merged to master/2.2
---
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
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/17905
ok Jenkins passes, I'm going to merge this in since there are a bunch of PR
failing because of this, even when they say it's up-to-date with master.
I'm going to investigate further though.
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17905
Merged build finished. Test PASSed.
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17905
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/76612/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17905
**[Test build #76612 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76612/testReport)**
for PR 17905 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17905
How about https://github.com/apache/spark/pull/17908? It tries to reset the
cataloged metadata objects and temporary objects.
---
If your project is set up for it, you can reply to this email
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/17905
right. I think it's a good way to decouple R tests from any earlier states
and also not to mask the error/leak. I'll get that in when Jenkins pass (and
see if I could figure out what is leaked)
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/17905
i see. I think
https://github.com/apache/spark/pull/17905/commits/d4c1a9db25ee7386f7b12e4dabb54210a9892510
is good. How about we get it checked in first (after jenkins passes)?
---
If your project
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/17905
hmm, spoke too soon I think - looks to me like all the `withTable` clause
are in place and complete.
not sure what can be leaking through then..
---
If your project is set up for it, you
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/17905
lgtm
---
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
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/17905
@falaki's PR did not actually trigger that test.
---
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
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/17905
@felixcheung you are right. That is the problem.
---
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
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/17905
I think this might be the reason? @yhuai @gatorsmile Am I reading these
right that these tables are created but never dropped?
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/17905
that I agree completely, @falaki - maybe we should audit the Scala SQL
tests - pretty sure R tests do not leave anything behind and only fails
apparently when running Scala tests before running
Github user falaki commented on the issue:
https://github.com/apache/spark/pull/17905
@felixcheung this approach is fine, but I think it is better if unit tests
do not leave any side-effects to begin with. In this case every test should
clean up state before and after (similar to
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17905
**[Test build #76612 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/76612/testReport)**
for PR 17905 at commit
19 matches
Mail list logo
