Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9126#issuecomment-148471724
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9137#issuecomment-148471677
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 pr
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9126#issuecomment-148471682
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 h
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/9051#issuecomment-148471371
@d2r can we get a screenshot here to help visualize the change? It'd be
great to do that for all UI changes.
---
If your project is set up for it, you can reply to this
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/9126#issuecomment-148471394
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
en
GitHub user mariusvniekerk opened a pull request:
https://github.com/apache/spark/pull/9137
[SPARK-10186][SQL] Array types using JDBCRDD and postgres
This change allows reading from jdbc array column types for the postgresql
dialect.
This also opens up some implementation f
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9061
---
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 enab
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/9061#issuecomment-148468064
Thanks - I've 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 th
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/9130#discussion_r42154786
--- Diff: core/src/main/scala/org/apache/spark/util/Utils.scala ---
@@ -2153,6 +2153,9 @@ private[spark] object Utils extends Logging {
conf.getInt("sp
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/9012#issuecomment-148467105
@NarineK Could you also bring this up to date with master branch ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHu
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9136#issuecomment-148466905
Unrelated failure, I'm going to merge soon anyway
---
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/9136#issuecomment-148465446
[Test build #1906 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1906/console)
for PR 9136 at commit
[`b72bc90`](https://github
Github user NarineK commented on the pull request:
https://github.com/apache/spark/pull/9012#issuecomment-148465208
yes, I'll do that. Let me know if you have any more comments ...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9136#issuecomment-148461262
[Test build #1906 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1906/consoleFull)
for PR 9136 at commit
[`b72bc90`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8416#issuecomment-148460264
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8416#issuecomment-148460253
[Test build #43792 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43792/console)
for PR 8416 at commit
[`318bc8c`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8416#issuecomment-148460269
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9076
---
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 enab
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8416#issuecomment-148459073
[Test build #43792 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43792/consoleFull)
for PR 8416 at commit
[`318bc8c`](https://gith
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9076#issuecomment-148458829
OK, merging 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 f
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9072#issuecomment-148457934
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9072#issuecomment-148457932
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8512#issuecomment-148457207
[Test build #43791 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43791/consoleFull)
for PR 8512 at commit
[`699c52b`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8416#issuecomment-148455905
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8416#issuecomment-148455862
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8512#issuecomment-148453660
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8512#issuecomment-148453594
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 h
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9114
---
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 enab
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9106
---
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 enab
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9072#issuecomment-148451518
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9072#issuecomment-148451543
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
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9106#issuecomment-148450771
Merging 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 featu
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9114#issuecomment-148450238
LGTM, I'll fix the nit while merging.
---
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
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/9114#discussion_r42148461
--- Diff:
launcher/src/test/java/org/apache/spark/launcher/SparkSubmitCommandBuilderSuite.java
---
@@ -80,7 +82,7 @@ public void testCliParser() throws Except
Github user squito commented on the pull request:
https://github.com/apache/spark/pull/8923#issuecomment-148445380
This looks good, but can you add a test case? Mostly I'd like to
understand the dependency structure that leads to this (perhaps there are other
corner cases related to
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/9118#discussion_r42146188
--- Diff: yarn/src/main/scala/org/apache/spark/deploy/yarn/Client.scala ---
@@ -340,6 +340,14 @@ private[spark] class Client(
"for alternatives."
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9118#issuecomment-148443924
So, I thought about this a little bit more and I think it would be worth it
to put that file in `createConfArchive` instead. That way, it's more efficient,
since it's one
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9127#issuecomment-148442913
[Test build #43789 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43789/consoleFull)
for PR 9127 at commit
[`25ba4b5`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9127#issuecomment-148440578
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9127#issuecomment-148440512
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 h
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9127#issuecomment-148439397
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 h
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9130#discussion_r42144562
--- Diff: core/src/main/scala/org/apache/spark/util/Utils.scala ---
@@ -2153,6 +2153,9 @@ private[spark] object Utils extends Logging {
conf.getIn
Github user jodersky commented on the pull request:
https://github.com/apache/spark/pull/9128#issuecomment-148438185
In general I agree with you, however since in this case some warnings (such
as deprecations) are not treated as fatal, the user gets a huge amount of
messages and
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9099#issuecomment-148431668
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9099#issuecomment-148431674
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9099#issuecomment-148431576
[Test build #43788 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43788/console)
for PR 9099 at commit
[`40d4d44`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9099#issuecomment-148430550
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9099#issuecomment-148430553
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9099#issuecomment-148430393
[Test build #43787 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43787/console)
for PR 9099 at commit
[`08d6dd1`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9099#issuecomment-148427409
[Test build #43788 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43788/consoleFull)
for PR 9099 at commit
[`40d4d44`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9099#issuecomment-148425914
[Test build #43787 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43787/consoleFull)
for PR 9099 at commit
[`08d6dd1`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9099#issuecomment-148424693
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9099#issuecomment-148424668
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9099#issuecomment-148422385
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9099#issuecomment-148422334
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 h
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9136#issuecomment-148417063
Yes that's fine. Feel free to spell-check more of the docs and zap many
typos in one go, if there are more.
---
If your project is set up for it, you can reply to this e
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9118#discussion_r42135926
--- Diff: yarn/src/main/scala/org/apache/spark/deploy/yarn/Client.scala ---
@@ -340,6 +340,14 @@ private[spark] class Client(
"for alternatives."
Github user squito commented on the pull request:
https://github.com/apache/spark/pull/9061#issuecomment-148409592
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 an
Github user markgrover commented on the pull request:
https://github.com/apache/spark/pull/9118#issuecomment-148409085
LGTM too, the tests seem to have passed as well.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If yo
Github user zero323 commented on the pull request:
https://github.com/apache/spark/pull/9099#issuecomment-148394778
It is there from 1.4.0.
Regarding tests I would prefer to wait until I get some clarification,
because right now I am not sure how to handle this.
---
If yo
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6841#issuecomment-148390637
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6841#issuecomment-148390634
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6841#issuecomment-148390469
[Test build #43785 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43785/console)
for PR 6841 at commit
[`8bd3e3d`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9136#issuecomment-148388802
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 pr
GitHub user brwe opened a pull request:
https://github.com/apache/spark/pull/9136
fix typo bellow -> below
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/brwe/spark typo-bellow
Alternatively you can review and apply these chang
Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/9134#discussion_r42121597
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala ---
@@ -655,6 +655,15 @@ object SparkSubmit {
// scalastyle:on println
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9135#issuecomment-148377755
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 pr
GitHub user philipphoffmann opened a pull request:
https://github.com/apache/spark/pull/9135
[SPARK-11129][MESOS] Link Spark WebUI from Mesos WebUI
Mesos has a feature for linking to frameworks running on top of Mesos
from the Mesos WebUI. This commit enables Spark to make use of
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9110#issuecomment-148374359
[Test build #1905 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1905/console)
for PR 9110 at commit
[`7a7d21e`](https://github
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9116#issuecomment-148371225
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9116#issuecomment-148371226
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9116#issuecomment-148371080
[Test build #43786 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43786/console)
for PR 9116 at commit
[`8060321`](https://github.
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9126#issuecomment-148361565
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 an
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9128#issuecomment-148360061
I think it's OK, but what does it help? if warnings are to be treated as
errors, they are errors like others. Does it become confusing to log an error
that says "warn"?
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9116#issuecomment-148359930
[Test build #43786 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43786/consoleFull)
for PR 9116 at commit
[`8060321`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9116#issuecomment-148358652
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9116#issuecomment-148358633
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 h
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9134#discussion_r42111793
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala ---
@@ -655,6 +655,15 @@ object SparkSubmit {
// scalastyle:on println
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6841#issuecomment-148357955
[Test build #43785 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43785/consoleFull)
for PR 6841 at commit
[`8bd3e3d`](https://gith
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/9116#issuecomment-148356952
@srowen Agree. I prefer to narrow the change of this PR, too. Reverted my
previous commit.
---
If your project is set up for it, you can reply to this email and have yo
Github user zjffdu commented on the pull request:
https://github.com/apache/spark/pull/9134#issuecomment-148356438
Check the test report. Seems the failed unit tests are unrelated.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6841#issuecomment-148354870
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6841#issuecomment-148354846
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9134#issuecomment-148353599
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9134#issuecomment-148353596
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9134#issuecomment-148353456
[Test build #43783 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43783/console)
for PR 9134 at commit
[`5b6e651`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6841#issuecomment-148350050
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6841#issuecomment-148350047
[Test build #43784 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43784/console)
for PR 6841 at commit
[`73d883d`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6841#issuecomment-148350051
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6841#issuecomment-148349753
[Test build #43784 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43784/consoleFull)
for PR 6841 at commit
[`73d883d`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9131#issuecomment-148349750
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 project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9131#issuecomment-148349751
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9131#issuecomment-148349695
**[Test build #43770 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43770/console)**
for PR 9131 at commit
[`424e937`](https://github
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6841#issuecomment-148349307
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6841#issuecomment-148349331
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
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/6841#discussion_r42108278
--- Diff: project/SparkBuild.scala ---
@@ -33,13 +33,17 @@ object BuildCommons {
private val buildLocation = file(".").getAbsoluteFile.getParentFi
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9116#issuecomment-148345442
Hm, this is getting unwieldy. There are several nested try blocks here. The
same argument goes for many of these methods -- if one fails should they not
continue trying?
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9110#issuecomment-148345206
[Test build #1905 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1905/consoleFull)
for PR 9110 at commit
[`7a7d21e`](https://git
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9110#issuecomment-148344776
OK thank you, I probably should have suspected it was on purpose. Seems OK
to me.
---
If your project is set up for it, you can reply to this email and have your
reply a
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/9061#issuecomment-148343787
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 a
401 - 500 of 584 matches
Mail list logo
