Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4315#issuecomment-73390500
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/4315#issuecomment-73387906
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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/4315#issuecomment-73368652
@pwendell or @JoshRosen could you tell Jenkins this is OK to test? I'm not
on the VIP list.
---
If your project is set up for it, you can reply to this email and have
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/4315#issuecomment-73387229
@srowen I've granted you admin permissions on the Spark pull request
builder, so you should now be able to whitelist PRs by yourself. Want to
comment here to test it
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4315#issuecomment-73388045
[Test build #27015 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27015/consoleFull)
for PR 4315 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4315#issuecomment-73390499
[Test build #27015 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27015/consoleFull)
for PR 4315 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/4315#issuecomment-73387260
Jenkins, this is 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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/4315
---
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 feature is
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/4315#issuecomment-73209414
LGTM, but looks like Jenkins hasn't tested this yet. Let me see if I am
able to whitelist you:
---
If your project is set up for it, you can reply to this email and have
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/4315#issuecomment-73209423
Jenkins, this is 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
Github user cjnolet commented on the pull request:
https://github.com/apache/spark/pull/4315#issuecomment-73173509
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
Github user medale commented on the pull request:
https://github.com/apache/spark/pull/4315#issuecomment-72785613
The problem was that the Spark project hive-exec 0.13.1a depends on
```
dependency
groupIdorg.apache.avro/groupId
artifactIdavro-mapred/artifactId
GitHub user medale opened a pull request:
https://github.com/apache/spark/pull/4315
[SPARK-3039] [BUILD] Spark assembly for new hadoop API (hadoop 2) contai...
...ns avro-mapred for
hadoop 1 API had been marked as resolved but did not work for at least some
builds due
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4315#issuecomment-72548453
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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/4315#issuecomment-72585857
OK, so this works because `spark-hive` brings this artifact back in, but
with the appropriate classifier? I suppose Maven treats artifacts with
different classifiers
15 matches
Mail list logo
