Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/51#issuecomment-36449820
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/12948/
---
If your project i
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/51#issuecomment-36449818
Merged build finished.
---
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 t
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/51
---
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 enable
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/51#issuecomment-36449552
Thanks @pwendell I merged 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 t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/51#issuecomment-36448975
Merged build triggered.
---
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 pull request:
https://github.com/apache/spark/pull/51#issuecomment-36448976
Merged build started.
---
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 th
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/51#issuecomment-36448947
Jenkins, 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
Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/51#issuecomment-36443418
Ah, I see. create-release.sh was handled in another PR.
---
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 markhamstra commented on the pull request:
https://github.com/apache/spark/pull/51#issuecomment-36442877
Looks good. The only remaining incubat* I find are in
dev/create-release/create-release.sh, but I'm not sure how you use that script.
---
If your project is set up fo
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/51#issuecomment-36442839
Merged build finished.
---
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 t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/51#issuecomment-36442840
One or more automated tests failed
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/12946/
---
If your pr
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/51#issuecomment-36442811
Merged build started.
---
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 th
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/51#issuecomment-36442810
Merged build triggered.
---
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 pwendell opened a pull request:
https://github.com/apache/spark/pull/51
Remove remaining references to incubation
This removes some loose ends not caught by the other (incubating -> tlp)
patches. @markhamstra this updates the version as you mentioned earlier.
You can me
14 matches
Mail list logo
