Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14390
@maver1ck this is already merged, leave it closed
---
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 fe
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14390
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14390
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63220/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14390
**[Test build #63220 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63220/consoleFull)**
for PR 14390 at commit
[`f009ee7`](https://github.com/apache/spark/commit/
Github user zzcclp commented on the issue:
https://github.com/apache/spark/pull/14390
@maver1ck I think you need to open another pr for change in Catalog.scala.
---
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 pro
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14390
**[Test build #63220 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63220/consoleFull)**
for PR 14390 at commit
[`f009ee7`](https://github.com/apache/spark/commit/f
Github user maver1ck commented on the issue:
https://github.com/apache/spark/pull/14390
@srowen
I missed one change in Catalog.scala
---
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 maver1ck commented on the issue:
https://github.com/apache/spark/pull/14390
Done.
Thank you.
---
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
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14390
Merged. @maver1ck you'll have to manually close it since the ASF bot won't
close PRs not open vs master.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14390
Ah, I get it now. I will merge this too then. Thank you.
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14390
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63131/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14390
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14390
**[Test build #63131 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63131/consoleFull)**
for PR 14390 at commit
[`ea2810f`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14390
**[Test build #63131 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63131/consoleFull)**
for PR 14390 at commit
[`ea2810f`](https://github.com/apache/spark/commit/e
Github user maver1ck commented on the issue:
https://github.com/apache/spark/pull/14390
As you merged https://github.com/apache/spark/pull/14459 I removed changes
in Dispatcher.scala.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitH
Github user maver1ck commented on the issue:
https://github.com/apache/spark/pull/14390
I know that.
And this patch is quite different. On master there are changes only in
Dispatcher.scala.
On branch-1.6 we need changes also in Catalog.scala.
---
If your project is set up f
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14390
We merge to master first and then cherry pick into other branches. Unless
the patch is quite different in other branches, we can just merge it into
others automatically.
---
If your project is set
Github user maver1ck commented on the issue:
https://github.com/apache/spark/pull/14390
Could you tell me why ?
We need different PR against different branches.
---
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
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14390
Can you close this PR please?
---
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 wi
Github user maver1ck commented on the issue:
https://github.com/apache/spark/pull/14390
I added another PR vs master. Using following command to find suspicious
code.
```
for i in `grep -c -R ConcurrentHashMap | grep -v ':0' | sed -e s/:.*//`; do
echo $i; grep keySet $i ; done
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14390
Ping @maver1ck
---
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
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14390
... but this needs to be opened vs master first. Don't worry about the
flaky test here.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14390
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 featur
Github user maver1ck commented on the issue:
https://github.com/apache/spark/pull/14390
@jkbradley
Could you look at it ?
I think this is problem from:
https://issues.apache.org/jira/browse/SPARK-10086
Maybe we should merge this PR to branch-1.6 before testing ?
https:
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14390
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14390
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62963/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14390
**[Test build #62963 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62963/consoleFull)**
for PR 14390 at commit
[`7bd4f44`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14390
**[Test build #62963 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62963/consoleFull)**
for PR 14390 at commit
[`7bd4f44`](https://github.com/apache/spark/commit/7
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14390
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62960/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14390
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14390
**[Test build #62960 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62960/consoleFull)**
for PR 14390 at commit
[`3ffbff1`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14390
**[Test build #62960 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62960/consoleFull)**
for PR 14390 at commit
[`3ffbff1`](https://github.com/apache/spark/commit/3
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14390
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14390
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62959/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14390
**[Test build #62959 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62959/consoleFull)**
for PR 14390 at commit
[`921e3c8`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14390
**[Test build #62959 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62959/consoleFull)**
for PR 14390 at commit
[`921e3c8`](https://github.com/apache/spark/commit/9
36 matches
Mail list logo
