Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/12182#issuecomment-206037026
@infynyxx I think this one is on the borderline. I would just create one so
everyone is happy.
---
If your project is set up for it, you can reply to this email
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12182#issuecomment-206032537
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12182#issuecomment-206032536
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12182#issuecomment-206032214
**[Test build #55020 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55020/consoleFull)**
for PR 12182 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12182#issuecomment-205983611
**[Test build #55020 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55020/consoleFull)**
for PR 12182 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12182#issuecomment-205982806
**[Test build #55019 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55019/consoleFull)**
for PR 12182 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/12182#issuecomment-205982721
Jenkins test 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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/12182#issuecomment-205982625
The change itself 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
Github user infynyxx commented on the pull request:
https://github.com/apache/spark/pull/12182#issuecomment-205982310
@hvanhovell I didn't create JIRA ticket because as per [Contributing
Guide](https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark)
creating JIRA
Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/12182#issuecomment-205979054
@infynyxx could you add a JIRA ticket and create a ticket like
`[SPARK-][BUILD] use https while downloading binaries` (see the titles of
other PRs).
---
If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12182#issuecomment-205978561
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 infynyxx opened a pull request:
https://github.com/apache/spark/pull/12182
use https while downloading binaries
## What changes were proposed in this pull request?
`./build/mvn` file was downloading binaries in non HTTPS mode. This PR
tends to fix it.
12 matches
Mail list logo