Github user zzcclp commented on a diff in the pull request:
https://github.com/apache/spark/pull/10608#discussion_r51677442
--- Diff: pom.xml ---
@@ -165,7 +165,7 @@
3.2.2
2.10.5
--- End diff --
@JoshRosen , why this version is 2.10.5, is it
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10608
---
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 ena
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-177098650
Merging this in master. Hopefully compilation will be faster.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as we
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-177098407
It's a bit hard to know whether the repl changes make sense or not, but I
think we just need to try it out and see if problems come up.
LGTM.
---
If your proje
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-177017642
Okay, I think this should now be ready for final review and sign-off.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-177000289
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-177000294
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-176999726
**[Test build #50401 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50401/consoleFull)**
for PR 10608 at commit
[`d24c31d`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-176943647
**[Test build #50401 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50401/consoleFull)**
for PR 10608 at commit
[`d24c31d`](https://gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-176703223
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-176703232
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-176702533
**[Test build #50367 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50367/consoleFull)**
for PR 10608 at commit
[`2c901e5`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-176657688
**[Test build #50367 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50367/consoleFull)**
for PR 10608 at commit
[`2c901e5`](https://gi
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-176652557
I think I found the problem: looks like `Utils.isInterp()` was returning
true even in non-interpreter code because of a small difference in how the 2.11
REPL works.
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-176646017
Looks like the problem might be related to
https://github.com/apache/spark/pull/9816: I think that the REPL log level is
being set to WARN, preventing the suite from
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-176638656
These look like legitimate test failures. It's a little tricky to reason
about which ones might be caused by this patch vs. longstanding 2.11
compatibility issues bec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-176635615
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-176635613
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-176635256
**[Test build #50343 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50343/consoleFull)**
for PR 10608 at commit
[`8dd36ab`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-176581286
**[Test build #50343 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50343/consoleFull)**
for PR 10608 at commit
[`8dd36ab`](https://gi
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-176579637
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-176552575
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-176552578
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-176551921
**[Test build #50321 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50321/consoleFull)**
for PR 10608 at commit
[`8dd36ab`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-176499509
**[Test build #50321 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50321/consoleFull)**
for PR 10608 at commit
[`8dd36ab`](https://gi
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-176016076
Want to fix the mima issue?
---
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 pull request:
https://github.com/apache/spark/pull/10608#issuecomment-175907259
**[Test build #50236 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50236/consoleFull)**
for PR 10608 at commit
[`18c5223`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-175907305
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-175907303
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-175903316
**[Test build #50236 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50236/consoleFull)**
for PR 10608 at commit
[`18c5223`](https://gi
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-175901624
@srowen, yep, this is pretty much just the result of running the version
changing and dep update scripts, followed by a grep through the documentation
and build to in
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-175901457
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
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10608#discussion_r51063981
--- Diff: sql/catalyst/pom.xml ---
@@ -127,13 +127,4 @@
-
-
-
--- End diff --
Nah, I think
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10608#discussion_r51053163
--- Diff: sql/catalyst/pom.xml ---
@@ -127,13 +127,4 @@
-
-
-
--- End diff --
Does this profil
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-175865873
That looks like what I'd expect -- roughly what you get from running the
change-version script and updating the list of dependencies?
---
If your project is set up for
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-175843132
/cc @srowen @pwendell @yhaui for review
---
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-175838017
**[Test build #50218 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50218/consoleFull)**
for PR 10608 at commit
[`18c5223`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-175838040
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-175838035
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-175835172
**[Test build #50218 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50218/consoleFull)**
for PR 10608 at commit
[`18c5223`](https://gi
GitHub user JoshRosen reopened a pull request:
https://github.com/apache/spark/pull/10608
[SPARK-6363][BUILD] Make Scala 2.11 the default Scala version
This patch changes Spark's build to make Scala 2.11 the default Scala
version. To be clear, this does not mean that Spark will stop
Github user JoshRosen closed the pull request at:
https://github.com/apache/spark/pull/10608
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-169208308
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-169208309
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-169208080
**[Test build #48796 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48796/consoleFull)**
for PR 10608 at commit
[`623a929`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-169168673
**[Test build #48796 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48796/consoleFull)**
for PR 10608 at commit
[`623a929`](https://gi
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/10608#issuecomment-169166671
Note: I'm happy to defer merging this pull request for a while. I just
happened to have the changes ready locally and figured that it would be nice to
test them on Je
GitHub user JoshRosen opened a pull request:
https://github.com/apache/spark/pull/10608
[SPARK-6363][BUILD] Make Scala 2.11 the default Scala version
This patch changes Spark's build to make Scala 2.11 the default Scala
version. To be clear, this does not mean that Spark will stop s
48 matches
Mail list logo
