Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11681
---
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/11681#issuecomment-204590621
Merged 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11681#issuecomment-204204935
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11681#issuecomment-204204937
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11681#issuecomment-204204607
**[Test build #54679 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54679/consoleFull)**
for PR 11681 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11681#issuecomment-204177330
**[Test build #54679 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54679/consoleFull)**
for PR 11681 at commit
Github user jodersky commented on the pull request:
https://github.com/apache/spark/pull/11681#issuecomment-204177309
FYI, I have two PRs pending to get the genjavadoc changes merged into
upstream. I haven't had any feedback yet so if anyone wants to have a look
please do
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11681#issuecomment-204176599
Ha yeah I've done that before in Sonatype.
---
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/11681#issuecomment-204176636
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
Github user brkyvz commented on the pull request:
https://github.com/apache/spark/pull/11681#issuecomment-204176323
@srowen I realized that I forgot to push the `release` button :( They've
been available under staging repositories at:
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11681#issuecomment-204175606
@brkyvz @mengxr it looks like the artifacts haven't pushed. Is it possible
to double-check what happened there?
---
If your project is set up for it, you can reply to
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11681#issuecomment-201815911
Thanks @brkyvz -- it doesn't look like it pushed yet but maybe there's a
delay. I can check again in a few days.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11681#issuecomment-201267646
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11681#issuecomment-201267649
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11681#issuecomment-201267629
**[Test build #54174 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54174/consoleFull)**
for PR 11681 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11681#issuecomment-201266846
**[Test build #54174 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54174/consoleFull)**
for PR 11681 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11681#issuecomment-201266637
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
Github user brkyvz commented on the pull request:
https://github.com/apache/spark/pull/11681#issuecomment-201076610
@mengxr @srowen @jaceklaskowski Jars are now published. They should be
available in a couple of hours if not already.
---
If your project is set up for it, you can
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/11681#issuecomment-200440418
I will do a cross build and @brkyvz will help publish the jars. cc:
@jodersky
---
If your project is set up for it, you can reply to this email and have your
reply
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11681#issuecomment-200295302
@mengxr is it possible to generate these plugins one more time for Scala
2.11.8 and 2.10.6? Maybe it's the last time we need to.
(Upstream now has plugins for
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11681#issuecomment-196934896
(Copying part of my email) This fails because we don't have the fork of
genjavadoc compiled for Spark 2.11.8.
We can see the org.spark-project packages here:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11681#issuecomment-196932794
Test FAILed.
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/11681#issuecomment-196932790
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11681#issuecomment-196932777
**[Test build #53206 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53206/consoleFull)**
for PR 11681 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11681#issuecomment-196931371
**[Test build #53206 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53206/consoleFull)**
for PR 11681 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11681#issuecomment-196931040
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 jaceklaskowski commented on the pull request:
https://github.com/apache/spark/pull/11681#issuecomment-196929219
@srowen Mind triggering a test? Thanks!
---
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/11681#issuecomment-196060987
Hey @jaceklaskowski, you should run `./dev/test-dependencies.sh
--replace-manifest` and commit the result in order to get the dependency tests
to pass.
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11681#issuecomment-195925992
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11681#issuecomment-195925993
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11681#issuecomment-195925990
**[Test build #53027 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53027/consoleFull)**
for PR 11681 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11681#issuecomment-195925848
**[Test build #53027 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53027/consoleFull)**
for PR 11681 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11681#issuecomment-195925765
This is OK for 2.x of course, and 1.6.x too I think. It's just a bug
release, and the 2.11 build is the secondary one for 1.6 anyway, so slightly
lower risk in any
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11681#issuecomment-195925741
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11681#issuecomment-195823387
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 jaceklaskowski opened a pull request:
https://github.com/apache/spark/pull/11681
[SPARK-13825][CORE] Upgrade to Scala 2.11.8
## What changes were proposed in this pull request?
Upgrade to 2.11.8 (from the current 2.11.7)
## How was this patch tested?
36 matches
Mail list logo
