Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/18148
It was an accident but it shouldn't cause any harm either.
---
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
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/18148
@vanzin Seems merging to branch-2.2 was an accident? Since it is not really
a bug fix, should we revert it from branch-2.2 and just keep it in the master?
---
If your project is set up for it, you
Github user rezasafi commented on the issue:
https://github.com/apache/spark/pull/18148
Soryy about this @vanzin. I didn't know that.
---
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 vanzin commented on the issue:
https://github.com/apache/spark/pull/18148
Oh crap, I didn't notice the branch. @rezasafi in the future, *always* send
PRs against the master branch first.
---
If your project is set up for it, you can reply to this email and have your
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/18148
@rezasafi please close this.
---
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 vanzin commented on the issue:
https://github.com/apache/spark/pull/18148
Merging to master.
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18148
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/18148
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77704/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18148
**[Test build #77704 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77704/testReport)**
for PR 18148 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18148
**[Test build #77704 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77704/testReport)**
for PR 18148 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/18148
retest this 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 wishes so,
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/18148
Fun, but probably unrelated:
```
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x7f115a81f0e9, pid=125279, tid=139711419225856
Github user rezasafi commented on the issue:
https://github.com/apache/spark/pull/18148
Not clear why the tests were 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/18148
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/18148
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77696/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18148
**[Test build #77696 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77696/testReport)**
for PR 18148 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18148
**[Test build #77696 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77696/testReport)**
for PR 18148 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18148
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/18148
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77666/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18148
**[Test build #77666 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77666/testReport)**
for PR 18148 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18148
**[Test build #77666 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77666/testReport)**
for PR 18148 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18148
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/18148
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77664/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18148
**[Test build #77664 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77664/testReport)**
for PR 18148 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18148
**[Test build #77664 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77664/testReport)**
for PR 18148 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/18148
Ah, yes. I read 'filter' instead of 'filterNot' in SparkBuild.scala where
it sets `mimaProjects`.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/18148
@vanzin the whole catalyst project is private.
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/18148
**[Test build #77659 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77659/testReport)**
for PR 18148 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18148
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/77659/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18148
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/18148
**[Test build #77659 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/77659/testReport)**
for PR 18148 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/18148
ok to 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 feature
enabled and wishes so, or if the
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18148
Can one of the admins verify this patch?
---
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
33 matches
Mail list logo
