Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8110#issuecomment-130069248
[Test build #40510 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40510/consoleFull)
for PR 8110 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8095
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/8096#issuecomment-130076101
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
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/8108#issuecomment-130077305
I'm going to merge this since Jenkins actually ran all the tests.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8096
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/8108
---
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/8111#issuecomment-130078089
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8111#issuecomment-130078148
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/4934
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8111#issuecomment-130078914
[Test build #40512 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40512/consoleFull)
for PR 8111 at commit
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/1290#issuecomment-130078928
I closed this PR. We can use Apache JIRA to continue discussion on
individual issues.
---
If your project is set up for it, you can reply to this email and have your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8111#issuecomment-130079899
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 mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/7429#discussion_r36800958
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/evaluation/BinaryClassificationMetrics.scala
---
@@ -51,6 +51,7 @@ class BinaryClassificationMetrics(
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8110#issuecomment-130081049
[Test build #40510 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40510/console)
for PR 8110 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8110#issuecomment-130081369
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/8111#issuecomment-130082123
[Test build #40513 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40513/consoleFull)
for PR 8111 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8104#issuecomment-130081987
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
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/8093#issuecomment-130082220
@markgrover can you post a screenshot?
---
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 jkbradley commented on the pull request:
https://github.com/apache/spark/pull/8077#issuecomment-130081656
Merging with master and branch-1.5
---
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/8038#issuecomment-130082015
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8111#issuecomment-130080388
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8079#issuecomment-130083164
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/7429#issuecomment-130082646
@mosessky I made one pass, and found only one issue commented inline.
Besides it, could you also add `since` tags to constructors? Thanks!
---
If your project is set up
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8111#issuecomment-130080431
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8077
---
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/7662#issuecomment-130083760
@XiaoqingWang Could you send the PR to the master branch as @yu-iskw
suggested?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/8038#issuecomment-130083914
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8084#issuecomment-130084411
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8084#issuecomment-130084392
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/7436
---
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/8038#issuecomment-130084399
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8038#issuecomment-130084424
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
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/7406#issuecomment-130084387
Thanks @BenFradet. Looks like @andrewor14 is working on this at the same
time to also get rid of the singleton TestSQLContext in order for his own tests
to pass.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8088#issuecomment-130084907
[Test build #40498 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40498/console)
for PR 8088 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8088#issuecomment-130084983
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 harishreedharan commented on a diff in the pull request:
https://github.com/apache/spark/pull/7739#discussion_r36802511
--- Diff: core/src/main/scala/org/apache/spark/deploy/Client.scala ---
@@ -68,7 +68,12 @@ private class ClientEndpoint(
val mainClass =
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8038#issuecomment-130085526
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/4380#issuecomment-130085889
@scwf looks like there is a real failure?
---
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 sethah opened a pull request:
https://github.com/apache/spark/pull/8112
[SPARK-8971][MLLIB][ML] Support balanced class labels when splitting
train/cross validation sets
I'm leaving a few comments about some of the design choices made in this PR.
- both
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8084#issuecomment-130087300
[Test build #1456 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1456/consoleFull)
for PR 8084 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8111#issuecomment-130087226
[Test build #1458 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1458/consoleFull)
for PR 8111 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8090#issuecomment-130087503
[Test build #1462 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1462/consoleFull)
for PR 8090 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8038#issuecomment-130086882
[Test build #1454 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1454/consoleFull)
for PR 8038 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8078#issuecomment-130087290
[Test build #1460 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1460/consoleFull)
for PR 8078 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6817#issuecomment-130087929
[Test build #1461 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1461/consoleFull)
for PR 6817 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8111#issuecomment-130087842
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/8112#issuecomment-130088223
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8033#issuecomment-130088956
[Test build #40518 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40518/consoleFull)
for PR 8033 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7411#issuecomment-130088895
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/8088#issuecomment-130088661
[Test build #1455 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1455/consoleFull)
for PR 8088 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8104#issuecomment-130088636
[Test build #1457 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1457/consoleFull)
for PR 8104 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8111#issuecomment-130079895
[Test build #40512 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40512/console)
for PR 8111 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7411#issuecomment-130088733
[Test build #40500 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40500/console)
for PR 7411 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8079#issuecomment-130069485
[Test build #40511 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40511/consoleFull)
for PR 8079 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7657#issuecomment-130072036
[Test build #40489 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40489/console)
for PR 7657 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7657#issuecomment-130072414
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/8095#issuecomment-130074997
I'm going to merge 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
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/8079#issuecomment-130081435
Uh oh, my proposal won't work currently, but I think it can be fixed.
Explanation here: [https://issues.apache.org/jira/browse/SPARK-9847]
---
If your project is
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8079#issuecomment-130083116
[Test build #40511 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40511/console)
for PR 8079 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8038#issuecomment-130081992
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
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/8088#issuecomment-130082406
LGTM2
---
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
Github user darkjh commented on the pull request:
https://github.com/apache/spark/pull/7874#issuecomment-130083455
Should I rebase this to the master to solve the build fail?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8104#issuecomment-130082221
[Test build #40515 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40515/consoleFull)
for PR 8104 at commit
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/8087#issuecomment-130082076
Yay it passed! If this looks reasonable, I'll make similar changes for the
other streaming ML pyspark tests.
---
If your project is set up for it, you can reply to
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/8104#issuecomment-130081441
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/7602#issuecomment-130082084
Hm, looks like this is failing the selenium suite. I would recommend not
making it a selenium suite but test it on a finer-grained level at the
`RDDOperationGraph`.
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/7380#issuecomment-130083493
@manishamde Could you make a pass?
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8104#issuecomment-130082016
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
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/7729#issuecomment-130083393
We don't need to add `since` tags for methods inherited from Java `Object`
like `toString`, `hashCode`, and `equals`. @sabhyankar Could you address
@MechCoder 's
Github user dbtsai commented on the pull request:
https://github.com/apache/spark/pull/8079#issuecomment-130084832
Then the most easy way is probably just overwriting the other when one is
set. :)
---
If your project is set up for it, you can reply to this email and have your
reply
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/7436#issuecomment-130084489
LGTM. Merged into master and branch-1.5. 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 markgrover commented on the pull request:
https://github.com/apache/spark/pull/8093#issuecomment-130084493
@andrewor14
[here](https://issues.apache.org/jira/secure/attachment/12749771/error_showing_in_UI.png)'s
the link from the JIRA.
---
If your project is set up for
Github user harishreedharan commented on a diff in the pull request:
https://github.com/apache/spark/pull/7739#discussion_r36802639
--- Diff:
core/src/main/scala/org/apache/spark/deploy/rest/SubmitRestProtocolRequest.scala
---
@@ -17,6 +17,8 @@
package
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/8079#issuecomment-130085747
That's true for the setter methods, but it doesn't work for fit() or
transform() given ParamMaps. fit and transform don't use the setter methods,
so we don't have a
Github user harishreedharan commented on a diff in the pull request:
https://github.com/apache/spark/pull/7739#discussion_r36802676
--- Diff:
core/src/main/scala/org/apache/spark/deploy/rest/StandaloneRestServer.scala ---
@@ -135,7 +135,10 @@ private[rest] class
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8111#issuecomment-130087782
[Test build #40513 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40513/console)
for PR 8111 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8038#issuecomment-130087846
[Test build #1454 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1454/console)
for PR 8038 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8111#issuecomment-130087421
[Test build #1459 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1459/consoleFull)
for PR 8111 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8084#issuecomment-130088381
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/8111#issuecomment-130088302
[Test build #1459 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1459/console)
for PR 8111 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8111#issuecomment-130088218
[Test build #1458 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1458/console)
for PR 8111 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8033#issuecomment-130088311
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8038#issuecomment-130088415
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/8033#issuecomment-130088255
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8090#issuecomment-130088400
[Test build #1462 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1462/console)
for PR 8090 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8088#issuecomment-130089159
[Test build #1455 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1455/console)
for PR 8088 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8078#issuecomment-130107721
[Test build #40508 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40508/console)
for PR 8078 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8115#issuecomment-130110321
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
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/8115#issuecomment-130110260
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/8115#issuecomment-130110297
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8111#issuecomment-130113781
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8109#issuecomment-130121610
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 jkbradley commented on the pull request:
https://github.com/apache/spark/pull/8087#issuecomment-130125941
@tdas Sure, I can do that. I don't think the race condition matters for
ML tests (or if it does, then the test was written incorrectly), but that does
clarify
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8119#discussion_r36817563
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveMetastoreCatalog.scala ---
@@ -888,6 +888,18 @@ private[hive] case class MetastoreRelation
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/8113#discussion_r36818586
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/aggregate/functions.scala
---
@@ -130,23 +138,36 @@ case class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8119#issuecomment-130129986
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7976#issuecomment-130130020
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8119#issuecomment-130130007
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7976#issuecomment-130129995
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8068#issuecomment-130134533
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
1 - 100 of 1363 matches
Mail list logo
