Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/1099#issuecomment-47190528
No, just want to see Jenkins happy.
---
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/1099#issuecomment-47190546
Jenkins, retest this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1099#issuecomment-47190746
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/1099#issuecomment-47190739
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/1223
---
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 opened a pull request:
https://github.com/apache/spark/pull/1225
[SPARK-2286][UI] Report exception/errors for failed tasks that are not
ExceptionFailure
Also added inline doc for each TaskEndReason.
You can merge this pull request into a Git repository by
Github user edrevo commented on the pull request:
https://github.com/apache/spark/pull/1211#issuecomment-47191917
I have added DSL support (`avg()`, `count(distinct())`...) following
@rxin's suggestion. I'm happy to change the DSL style if you end up favoring
the other approach.
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1225#discussion_r14226878
--- Diff: core/src/main/scala/org/apache/spark/TaskEndReason.scala ---
@@ -30,27 +30,67 @@ import org.apache.spark.storage.BlockManagerId
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1225#issuecomment-47191925
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/1099#issuecomment-47191952
Merged build finished.
---
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/1099#issuecomment-47191953
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16138/
---
If your project is set up for it, you can
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1225#discussion_r14226907
--- Diff: core/src/main/scala/org/apache/spark/TaskEndReason.scala ---
@@ -30,27 +30,67 @@ import org.apache.spark.storage.BlockManagerId
@DeveloperApi
GitHub user ueshin opened a pull request:
https://github.com/apache/spark/pull/1226
[SPARK-2287] [SQL] Make ScalaReflection be able to handle Generic case
classes.
You can merge this pull request into a Git repository by running:
$ git pull
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1225#discussion_r14227125
--- Diff: core/src/main/scala/org/apache/spark/TaskEndReason.scala ---
@@ -58,10 +98,19 @@ case class ExceptionFailure(
* it was fetched.
*/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1225#issuecomment-47192750
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/1225#issuecomment-47192746
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/1226#issuecomment-47192751
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 ueshin commented on the pull request:
https://github.com/apache/spark/pull/1226#issuecomment-47192918
This will cause merge conflict with #1193, but I can fix it soon.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1193#issuecomment-47193347
Merging this one so you can fix the conflict with this other.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1193
---
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 ueshin commented on the pull request:
https://github.com/apache/spark/pull/1193#issuecomment-47193596
@rxin Thanks! I will fix soon.
---
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 jegonzal commented on the pull request:
https://github.com/apache/spark/pull/1217#issuecomment-47193665
I spent some time verifying the math behind the PageRank (in particular
starting values) to ensure that the delta formulation behaves identically to
the static
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1217#issuecomment-47193690
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/1217#issuecomment-47193686
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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1225#discussion_r14227540
--- Diff: core/src/main/scala/org/apache/spark/ui/jobs/StagePage.scala ---
@@ -283,12 +283,7 @@ private[ui] class StagePage(parent: JobProgressTab)
extends
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1225#issuecomment-47193773
This is a pretty straightforward change. Looks good to me providing that
the stack trace looks alright and tests pass.
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1217#issuecomment-47193791
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16142/
---
If your project is set up for it, you can
Github user jegonzal commented on a diff in the pull request:
https://github.com/apache/spark/pull/1217#discussion_r14227560
--- Diff: graphx/src/main/scala/org/apache/spark/graphx/Pregel.scala ---
@@ -158,4 +169,125 @@ object Pregel extends Logging {
g
} // end of
Github user jegonzal commented on a diff in the pull request:
https://github.com/apache/spark/pull/1217#discussion_r14227573
--- Diff: graphx/src/main/scala/org/apache/spark/graphx/Pregel.scala ---
@@ -158,4 +169,125 @@ object Pregel extends Logging {
g
} // end of
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1225#issuecomment-47194199
Merged build finished.
---
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/1225#issuecomment-47194200
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16139/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/964#issuecomment-47194339
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/1217#issuecomment-47194334
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/964#issuecomment-47194330
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 ueshin commented on the pull request:
https://github.com/apache/spark/pull/1226#issuecomment-47194382
Fixed merge conflict with #1193.
---
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/1226#issuecomment-47194327
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/1217#issuecomment-47194328
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/1226#issuecomment-47194335
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/1217#issuecomment-47194448
Merged build finished.
---
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/1217#issuecomment-47194450
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16144/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1217#issuecomment-47196045
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/1217#issuecomment-47196054
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/1217#issuecomment-47196162
Merged build finished.
---
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/1217#issuecomment-47196163
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16146/
---
If your project is set up for it, you can
Github user xiajunluan commented on the pull request:
https://github.com/apache/spark/pull/931#issuecomment-47196343
@pwendell I will update the codes soon, thanks for reminder.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1226#issuecomment-47197537
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/1226#issuecomment-47197529
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/1225#issuecomment-47198182
Jenkins, retest this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1225#issuecomment-47198281
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/1225#issuecomment-47198289
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 opened a pull request:
https://github.com/apache/spark/pull/1227
Removed throwable field from FetchFailedException and added
MetadataFetchFailedException
FetchFailedException used to have a Throwable field, but in reality we
never propogate any of the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1227#issuecomment-47198650
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/1227#issuecomment-47198635
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/1217#issuecomment-47198651
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 vrilleup commented on the pull request:
https://github.com/apache/spark/pull/964#issuecomment-47198628
multiply function is RowMatrix was using dense matrix - sparse vector
multiplication function, but in current breeze version there is no
implementation for this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1217#issuecomment-47198638
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/1217#issuecomment-47198800
Merged build finished.
---
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/1217#issuecomment-47198803
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16150/
---
If your project is set up for it, you can
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/991#discussion_r14229594
--- Diff: core/src/main/java/org/apache/spark/Service.java ---
@@ -0,0 +1,97 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1226#issuecomment-47199290
Merged build finished.
---
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/1226#issuecomment-47199289
Merged build finished.
---
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/1225#issuecomment-47199293
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16141/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/964#issuecomment-47199297
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16145/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1225#issuecomment-47199288
Merged build finished.
---
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/1226#issuecomment-47199294
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16143/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1226#issuecomment-47199296
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16140/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1228#issuecomment-47199424
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/1228#issuecomment-47199418
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/1225#issuecomment-47200164
There was a unit test failure that my latest push fixed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1225#issuecomment-47200218
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 jegonzal commented on the pull request:
https://github.com/apache/spark/pull/1228#issuecomment-47200276
@ankurdave thanks for pointing out this bug!
---
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/1225#issuecomment-47200208
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/1226#issuecomment-47201129
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16147/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1226#issuecomment-47201127
Merged build finished.
---
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 egraldlo commented on a diff in the pull request:
https://github.com/apache/spark/pull/1190#discussion_r14230460
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkStrategies.scala ---
@@ -65,7 +64,7 @@ private[sql] abstract class SparkStrategies
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1225#issuecomment-47201642
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16148/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1225#issuecomment-47201641
Merged build finished.
---
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/1227#issuecomment-47202409
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16149/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1227#issuecomment-47202408
Merged build finished. All automated tests passed.
---
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/1228#issuecomment-47202811
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16151/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1228#issuecomment-47202809
Merged build finished.
---
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 opened a pull request:
https://github.com/apache/spark/pull/1229
[SPARK-2251] fix concurrency issues in random sampler
The following code is very likely to throw an exception:
~~~
val rdd = sc.parallelize(0 until 111, 10).sample(false, 0.1)
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1229#issuecomment-47203216
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/1229#issuecomment-47203207
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/1229#issuecomment-47203638
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/1229#issuecomment-47203628
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/1225#issuecomment-47203899
Merged build finished. All automated tests passed.
---
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/1225#issuecomment-47203901
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16152/
---
If your
Github user li-zhihui commented on a diff in the pull request:
https://github.com/apache/spark/pull/900#discussion_r14231480
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedSchedulerBackend.scala
---
@@ -244,6 +255,17 @@ class
Github user jegonzal commented on the pull request:
https://github.com/apache/spark/pull/1217#issuecomment-47204112
@ankurdave and @rxin there is an issue with the current API. The
`sendMessage` function pull the active field out of the vertex value here:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1229#issuecomment-47204535
Merged build finished.
---
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/1229#issuecomment-47204537
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16154/
---
If your project is set up for it, you can
Github user li-zhihui commented on the pull request:
https://github.com/apache/spark/pull/900#issuecomment-47204723
@tgravescs @kayousterhout
I add a new commit
* Move waitBackendReady to TaskSchedulerImpl.start
* Code refactor by @kayousterhout 's comments
---
If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1229#issuecomment-47204966
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/1229#issuecomment-47204976
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 li-zhihui commented on a diff in the pull request:
https://github.com/apache/spark/pull/900#discussion_r14232018
--- Diff:
yarn/common/src/main/scala/org/apache/spark/scheduler/cluster/YarnClusterSchedulerBackend.scala
---
@@ -0,0 +1,51 @@
+/*
+ * Licensed to
Github user ueshin commented on the pull request:
https://github.com/apache/spark/pull/1226#issuecomment-47206743
Could you please retest this?
Previous tests seemed like Hive metastore was something wrong.
(Can I let Jenkins do retest?)
---
If your project is set up for it,
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/991#discussion_r14232502
--- Diff: core/src/main/java/org/apache/spark/Service.java ---
@@ -0,0 +1,97 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1229#issuecomment-47206910
Merged build finished.
---
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/1229#issuecomment-47206911
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16153/
---
If your project is set up for it, you can
1 - 100 of 408 matches
Mail list logo
