Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/233#issuecomment-38891456
Merged build triggered. Some tests failed or tests have not started
running yet.
---
If your project is set up for it, you can reply to this email and have your
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/158#discussion_r11056053
--- Diff:
core/src/main/scala/org/apache/spark/storage/TachyonBlockManager.scala ---
@@ -0,0 +1,164 @@
+/*
+ * Licensed to the Apache Software
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/158#discussion_r11056067
--- Diff:
core/src/main/scala/org/apache/spark/storage/TachyonBlockManager.scala ---
@@ -0,0 +1,164 @@
+/*
+ * Licensed to the Apache Software
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/251#issuecomment-38891805
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/124#issuecomment-38891808
Merged build started. Some tests failed or tests have not started running
yet.
---
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/251#issuecomment-38891806
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13539/
---
If your project
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/158#issuecomment-38892147
Hey @RongGu I think this can be simplified a lot by just putting all of the
RDD blocks inside of the application's Tachyon directory.
This patch in general has
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/124#issuecomment-38892476
Adding test would mean a lot of code i.e. a project for each test. Like this
https://github.com/scalastyle/scalastyle-sbt-plugin/tree/master/src
---
If your
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/258
---
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/260#issuecomment-38893514
Merged build finished. Some tests failed or tests have not started running
yet.
---
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/124#issuecomment-38894019
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/124#issuecomment-38894020
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13541/
---
If your project
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/124#issuecomment-38894225
Thanks I 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 this
GitHub user ScrapCodes opened a pull request:
https://github.com/apache/spark/pull/261
Comment style space before ending */ check.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ScrapCodes/spark-1 comment-style-check2
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/124
---
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/261#issuecomment-38895125
Merged build started. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/261#issuecomment-38895374
Merged build triggered. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/261#issuecomment-38895382
Merged build started. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/261#issuecomment-38897930
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13543/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/261#issuecomment-38897929
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/261#issuecomment-38898283
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/261#issuecomment-38898284
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13544/
---
If your project
Github user logc commented on the pull request:
https://github.com/apache/spark/pull/134#issuecomment-38899714
It seems there is no interest in my proposal. If the Jenkins server
complains again in 2 weeks, I will just close the PR. Thanks.
---
If your project is set up for it,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/186#issuecomment-38909356
Merged build triggered. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user darabos commented on the pull request:
https://github.com/apache/spark/pull/181#issuecomment-38909539
Sorry, the delay is my fault. I was too busy to get around to the test so
far, but I still intend to do it. At least I've _read_ some Spark tests :).
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/186#issuecomment-38912726
Build is starting -or- tests failed to complete.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13545/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/186#issuecomment-38913218
Merged build started. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/186#issuecomment-38913205
Merged build triggered. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/262#issuecomment-38915063
Merged build triggered. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply
GitHub user ScrapCodes opened a pull request:
https://github.com/apache/spark/pull/262
SPARK-1336 Reducing the output of run-tests script.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ScrapCodes/spark-1
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/186#issuecomment-38917238
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13546/
---
If your project
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/186#issuecomment-38917608
Finally, Jenkins comes back to normal, thank you @pwendell for your work to
fix this
@kayousterhout @mateiz @markhamstra how about the current one? I think
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/262#issuecomment-38919705
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 LIDIAgroup commented on a diff in the pull request:
https://github.com/apache/spark/pull/216#discussion_r11065687
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/util/InfoTheory.scala
---
@@ -0,0 +1,49 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/186#issuecomment-38932507
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/195#issuecomment-38935838
Merged build triggered. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/195#issuecomment-38935866
Merged build started. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/263#issuecomment-38933434
Merged build started. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/259#issuecomment-38940020
Merged build triggered. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/259#issuecomment-38940042
Merged build started. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user darabos commented on the pull request:
https://github.com/apache/spark/pull/119#issuecomment-38927661
Hi! I'd like to use TestUtils from this pull request in
https://github.com/apache/spark/pull/181. If this pull request needs more time,
perhaps the TestUtils code could
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/195#issuecomment-38942145
Build is starting -or- tests failed to complete.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13550/
IIRC it didn't seem to be picking up runtime-scope dependencies in the
classpath. It could be a plugin rather than scalac issue. Easy to check if
you like by uncommenting, but I expect that it will have the same result.
It is not so harmful; just means there classes are visible at compile time
in
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/79#discussion_r11074467
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/tree/impurity/Impurity.scala ---
@@ -0,0 +1,42 @@
+/*
+ * Licensed to the Apache Software
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/186#discussion_r11068021
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -119,18 +122,31 @@ class DAGScheduler(
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/186#issuecomment-38934195
ehrecovery with file input stream case in streaming part failed,
which is a bit weird,
I met it for 3 times now, I think Mark also met it yesterday,
Github user darabos commented on the pull request:
https://github.com/apache/spark/pull/181#issuecomment-38928010
I couldn't figure out how to get a separate jar built for use in this test.
(I'm new to Java/Scala build systems.) Anyway you say it would be brittle. I'll
just wait for
Github user haoyuan commented on the pull request:
https://github.com/apache/spark/pull/158#issuecomment-38946585
@pwendell I forgot the exact number. But if you have tens or hundreds of
thousands, the operation in the folder will be slowed down.
---
If your project is set up for
Github user haoyuan commented on the pull request:
https://github.com/apache/spark/pull/158#issuecomment-38946828
Wouldn't changing the default sub-folders number to a smaller one solve the
issue? e.g. shuffleManager.conf.get(spark.tachyonStore.subDirectories,
4).toInt
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/195#issuecomment-38936429
Merged build started. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user mathonsunday commented on the pull request:
https://github.com/apache/spark/pull/260#issuecomment-38938443
I'm on a Mac with OS X Mavericks
---
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/158#issuecomment-38948030
Build started. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/158#issuecomment-38948004
Build triggered. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/186#issuecomment-38932509
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13548/
---
If your project
Github user nicklan commented on the pull request:
https://github.com/apache/spark/pull/258#issuecomment-38948413
Some of this is unfortunately a bug in the tachyon scripts. I'll submit a
PR there to get them fixed. Not sure it not being able to find the main
class however,
GitHub user tgravescs opened a pull request:
https://github.com/apache/spark/pull/263
SPARK-1345 adding missing dependency on avro for hadoop 0.23 to the new ...
...sql pom files
You can merge this pull request into a Git repository by running:
$ git pull
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/79#discussion_r11077636
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/tree/impurity/Impurity.scala ---
@@ -0,0 +1,42 @@
+/*
+ * Licensed to the Apache Software
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/186#discussion_r11068107
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -140,8 +156,8 @@ class DAGScheduler(
/**
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/158#issuecomment-38950091
@haoyuan hey HY - the issue is mostly around keeping the complexity of the
code minimal and avoiding a bunch of code duplication. The code around deleting
this
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/158#discussion_r11078295
--- Diff: docs/scala-programming-guide.md ---
@@ -265,11 +265,24 @@ A complete list of actions is available in the [RDD
API doc](api/core/index.html
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/158#issuecomment-38951266
@haoyuan how about this. Could we add a `TODO` in `TachyonStore` that says
something like this:
```
TODO: Some of the logic here could be
Github user AndreSchumacher commented on a diff in the pull request:
https://github.com/apache/spark/pull/195#discussion_r11072079
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/parquet/ParquetRelation.scala ---
@@ -72,16 +71,56 @@ case class ParquetRelation(val tableName:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/263#issuecomment-38939758
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 AndreSchumacher commented on a diff in the pull request:
https://github.com/apache/spark/pull/195#discussion_r11071279
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/parquet/ParquetTableOperations.scala
---
@@ -40,7 +40,7 @@ import java.util.Date
*
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/263#issuecomment-38933421
Merged build triggered. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/263#issuecomment-38939759
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13549/
---
If your project
Github user RongGu commented on the pull request:
https://github.com/apache/spark/pull/158#issuecomment-38953146
Hey Rong,
I just didn't know this was necessary in Tachyon. But if we keep it, yes
let's just keep the number of directories at 64. The main issue was just
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/158#issuecomment-38953683
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. If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/158#issuecomment-38953685
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13553/
---
If your project
Github user RongGu commented on the pull request:
https://github.com/apache/spark/pull/158#issuecomment-38955388
I've set number of directories in TachyonStore back to 64 and added a TODO
tag now. I've already tested it and tried it out locally. Keep me informed
:)
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/158#issuecomment-38956288
Build triggered. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/158#issuecomment-38956305
Build started. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/158#issuecomment-38956807
Build started. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/158#issuecomment-38956788
Build triggered. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/186#discussion_r11068295
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -119,18 +122,31 @@ class DAGScheduler(
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/158#issuecomment-38960111
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13554/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/158#issuecomment-38960110
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. If your
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/158#discussion_r11083003
--- Diff: core/src/main/scala/org/apache/spark/storage/TachyonStore.scala
---
@@ -0,0 +1,127 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/158#issuecomment-38961453
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. If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/158#issuecomment-38961560
Build triggered. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/158#issuecomment-38961571
Build started. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
GitHub user nicklan opened a pull request:
https://github.com/apache/spark/pull/264
fix path for jar, make sed actually work on OSX
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nicklan/spark make-distribution-fixes
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/264#issuecomment-38962048
Merged build started. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/158#discussion_r11083997
--- Diff: core/src/main/scala/org/apache/spark/storage/TachyonStore.scala
---
@@ -0,0 +1,127 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/158#issuecomment-38964161
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. If your
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/264#issuecomment-38964996
Thanks Nick, tested locally and merged.
---
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/158#issuecomment-38969035
Build started. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/265#issuecomment-38970923
Merged build triggered. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/265#issuecomment-38970939
Merged build started. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/265#issuecomment-38971066
Build is starting -or- tests failed to complete.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13560/
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/251#discussion_r11087320
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/LiveListenerBus.scala ---
@@ -1,101 +1,119 @@
-/*
- * Licensed to the Apache Software
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/265#issuecomment-38973045
Merged build triggered. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/158#issuecomment-38973433
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13559/
---
If your project
GitHub user aarondav opened a pull request:
https://github.com/apache/spark/pull/267
SPARK-1349: spark-shell gets its own command history
Currently, spark-shell shares its command history with scala repl.
This fix is simply a modification of the default FileBackedHistory
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/267#issuecomment-38974160
Merged build started. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/267#issuecomment-38974154
Merged build triggered. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/266#issuecomment-38976597
Merged build finished. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user sryza commented on a diff in the pull request:
https://github.com/apache/spark/pull/30#discussion_r11089191
--- Diff: python/Makefile ---
@@ -0,0 +1,7 @@
+assembly: clean
+ python setup.py build --build-lib build/lib
+ unzip lib/py4j*.zip -d build/lib
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/265#issuecomment-38976773
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13562/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/267#issuecomment-38977253
Merged build finished. Build is starting -or- tests failed to complete.
---
If your project is set up for it, you can reply to this email and have your
reply appear
1 - 100 of 123 matches
Mail list logo
