Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6651#issuecomment-109045784
Filed https://issues.apache.org/jira/browse/SPARK-8109 to fix the MiMa
problem.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user kayousterhout commented on a diff in the pull request:
https://github.com/apache/spark/pull/6652#discussion_r31764493
--- Diff: core/src/main/scala/org/apache/spark/MapOutputTracker.scala ---
@@ -232,6 +232,12 @@ private[spark] class MapOutputTrackerMaster(conf:
Github user kayousterhout commented on a diff in the pull request:
https://github.com/apache/spark/pull/6652#discussion_r31765446
--- Diff: core/src/main/scala/org/apache/spark/MapOutputTracker.scala ---
@@ -232,6 +232,12 @@ private[spark] class MapOutputTrackerMaster(conf:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6651#issuecomment-109056237
[Test build #34209 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34209/consoleFull)
for PR 6651 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6651#issuecomment-109056271
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 harsha2010 opened a pull request:
https://github.com/apache/spark/pull/6654
[SPARK-7546][ml] An example of a complex ml pipeline
@jkbradley can you please review? I took 20newsgroups dataset as an example
for a ML pipeline. Since multiclass evaluator does not exist in
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6627#issuecomment-109060685
[Test build #34215 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34215/consoleFull)
for PR 6627 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6654#issuecomment-109062895
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 tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/6632#discussion_r31769636
--- Diff:
external/kafka/src/main/scala/org/apache/spark/streaming/kafka/KafkaRDD.scala
---
@@ -60,6 +62,49 @@ class KafkaRDD[
}.toArray
}
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/6360#discussion_r31769642
--- Diff: yarn/src/main/scala/org/apache/spark/deploy/yarn/Client.scala ---
@@ -296,6 +284,53 @@ private[spark] class Client(
}
/**
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/6360#discussion_r31769565
--- Diff: yarn/src/main/scala/org/apache/spark/deploy/yarn/Client.scala ---
@@ -296,6 +284,53 @@ private[spark] class Client(
}
/**
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/6632#discussion_r31771864
--- Diff:
external/kafka/src/main/scala/org/apache/spark/streaming/kafka/KafkaRDD.scala
---
@@ -60,6 +62,49 @@ class KafkaRDD[
}.toArray
}
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/6620#issuecomment-109074383
LGTM, 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 project does not have this feature
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6360#discussion_r31773187
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala ---
@@ -315,62 +315,59 @@ object SparkSubmit {
case _ =
}
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/6625#discussion_r31776659
--- Diff:
core/src/main/scala/org/apache/spark/serializer/SerializationDebugger.scala ---
@@ -145,17 +151,50 @@ private[spark] object
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6659#issuecomment-109092254
[Test build #34223 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34223/consoleFull)
for PR 6659 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6661#issuecomment-109095713
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/6661#issuecomment-109095725
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/6655#issuecomment-109095790
Can you add a docstring test for 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6660#issuecomment-109099916
[Test build #34227 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34227/consoleFull)
for PR 6660 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6660#issuecomment-109102894
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/6660#issuecomment-109102888
[Test build #34231 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34231/consoleFull)
for PR 6660 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6638#issuecomment-109106713
[Test build #34234 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34234/consoleFull)
for PR 6638 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6645#issuecomment-109121914
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/6508#issuecomment-109137899
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/6508#issuecomment-109137850
[Test build #34233 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34233/consoleFull)
for PR 6508 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6660#discussion_r31783787
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/codegen/CodeGenerator.scala
---
@@ -685,13 +163,106 @@ abstract class
Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/6647#discussion_r31784183
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -130,13 +130,29 @@ class Analyzer(
}
Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/6647#discussion_r31784199
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -130,13 +130,29 @@ class Analyzer(
}
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6663#issuecomment-109143338
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 chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/6647#discussion_r31784226
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -130,13 +130,29 @@ class Analyzer(
}
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6663#issuecomment-109143336
[Test build #34243 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34243/consoleFull)
for PR 6663 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6360#issuecomment-109151277
[Test build #34249 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34249/consoleFull)
for PR 6360 at commit
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/6607#discussion_r31785869
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/scheduler/ReceiverTracker.scala
---
@@ -308,12 +305,41 @@ class ReceiverTracker(ssc:
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/6607#discussion_r31785926
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/scheduler/ReceiverTracker.scala
---
@@ -308,12 +305,41 @@ class ReceiverTracker(ssc:
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/6659#issuecomment-109156747
LGTM. We can test this in PR #6614
---
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 tdas commented on the pull request:
https://github.com/apache/spark/pull/6614#issuecomment-109156834
I am going to merge #6659 to prevent negative numbers in the UI. Could you
please merge with the master after that PR is merged to verify that there are
no negative
Github user dibbhatt commented on the pull request:
https://github.com/apache/spark/pull/6614#issuecomment-109158036
Sure
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6360#issuecomment-109157984
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/5889#issuecomment-109166951
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/5889#issuecomment-109166959
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 vanzin opened a pull request:
https://github.com/apache/spark/pull/6664
[minor] [build] Change link to jenkins builds on github.
Link to the tail of the console log, instead of the full log. That's
bound to have the info the user is looking for, and at the same time
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/6664#issuecomment-109166963
/cc @shaneknapp
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/6656
---
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 shivaram commented on the pull request:
https://github.com/apache/spark/pull/6642#issuecomment-109167564
The file is now up at
https://s3-us-west-2.amazonaws.com/sparkr-data/flights.csv
---
If your project is set up for it, you can reply to this email and have your
reply
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/5694#issuecomment-109167677
Given that there's some messiness in reading bash error code scripts here,
etc. do you think it would be a net reduction of complexity to just include
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6664#issuecomment-109167542
[Test build #34254 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34254/consoleFull)
for PR 6664 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6499#issuecomment-109171000
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/6660#issuecomment-109101826
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/6660#issuecomment-109104926
[Test build #34232 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34232/consoleFull)
for PR 6660 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6660#issuecomment-109104786
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/6659#issuecomment-109114442
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/6661#issuecomment-109121559
[Test build #34237 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34237/consoleFull)
for PR 6661 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6652#issuecomment-109121081
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 shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/6652#discussion_r31782198
--- Diff: core/src/main/scala/org/apache/spark/MapOutputTracker.scala ---
@@ -284,6 +291,41 @@ private[spark] class MapOutputTrackerMaster(conf:
SparkConf)
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6652#issuecomment-109121314
[Test build #34239 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34239/consoleFull)
for PR 6652 at commit
Github user shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/6652#discussion_r31782208
--- Diff: core/src/main/scala/org/apache/spark/MapOutputTracker.scala ---
@@ -284,6 +291,41 @@ private[spark] class MapOutputTrackerMaster(conf:
SparkConf)
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6661#issuecomment-109121050
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6656#issuecomment-109121659
[Test build #34238 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34238/consoleFull)
for PR 6656 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6647#issuecomment-109122764
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/6647#issuecomment-109122774
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 chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/6638#issuecomment-109122581
@viirya I think this PR just for fixing the bug when user specify the
output schema, but #5688 will be more general to support user specified SerDe
(and also the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6647#issuecomment-109125817
[Test build #34241 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34241/consoleFull)
for PR 6647 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6647#issuecomment-109125832
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/6662#issuecomment-109126190
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/6661#issuecomment-109158584
[Test build #34246 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34246/consoleFull)
for PR 6661 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6661#issuecomment-109158590
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6361#issuecomment-109171615
Trying to dig into the stracktrace a bit:, here an excerpt from
GenericUDTFExplode.java in hive-exec-0.13.1a-sources.jar:
```java
private transient
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/6651#issuecomment-109103906
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6638#issuecomment-109105284
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/6638#issuecomment-109105311
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6659#issuecomment-109114412
[Test build #34223 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34223/consoleFull)
for PR 6659 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6616#issuecomment-109113758
[Test build #34235 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34235/consoleFull)
for PR 6616 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/6656#issuecomment-109120493
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 liancheng commented on the pull request:
https://github.com/apache/spark/pull/6597#issuecomment-109120221
@JoshRosen @vanzin Filed SPARK-8118 for this. Adjusting
`ParquetRelation.enableLogForwarding()` should fix this.
---
If your project is set up for it, you can reply
Github user kostya-sh commented on the pull request:
https://github.com/apache/spark/pull/6597#issuecomment-109142263
BTW `enableLogForwarding()` should be updated as well, because name of the
logger has been changed to `org.apache.parquet`. From parquet-mr Log:
// add a
Github user XuTingjun commented on the pull request:
https://github.com/apache/spark/pull/6643#issuecomment-109142206
Thanks all, I have updated the code, please have a look again.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6663#issuecomment-109147529
Cool, HiveCompatibilitySuite now runs in 12 minutes.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6360#issuecomment-109151103
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/6360#issuecomment-109151114
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 tdas commented on the pull request:
https://github.com/apache/spark/pull/6607#issuecomment-109154567
I added some comments. At a highlevel 2 things are needed
- better allocation algorithm,
- tests.
---
If your project is set up for it, you can reply to this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6499#issuecomment-109156892
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/6499#issuecomment-109156903
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6627#issuecomment-109166348
[Test build #34252 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34252/consoleFull)
for PR 6627 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/6656#issuecomment-109166861
Thanks. Merging in master and branch-1.4 so it will be available in 1.4.1
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6650#discussion_r31788825
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedSchedulerBackend.scala
---
@@ -103,7 +103,7 @@ class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5889#issuecomment-109168776
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/6651
---
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/6652#issuecomment-109111845
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/6652#issuecomment-109111833
[Test build #34222 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34222/consoleFull)
for PR 6652 at commit
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/5688#discussion_r31781862
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/execution/HiveQuerySuite.scala
---
@@ -455,7 +464,7 @@ class HiveQuerySuite extends
Github user shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/6652#discussion_r31782160
--- Diff: core/src/test/scala/org/apache/spark/MapOutputTrackerSuite.scala
---
@@ -205,4 +205,29 @@ class MapOutputTrackerSuite extends SparkFunSuite {
Github user shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/6652#discussion_r31782152
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -137,6 +137,15 @@ class DAGScheduler(
private[scheduler] val
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6656#issuecomment-109121032
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/6656#issuecomment-109121049
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/6661#issuecomment-109121028
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/6652#issuecomment-109121038
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/6645#issuecomment-109122311
[Test build #34240 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34240/consoleFull)
for PR 6645 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6645#issuecomment-109121920
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/6607#issuecomment-109137039
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
1 - 100 of 881 matches
Mail list logo
