Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7081#issuecomment-116590953
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/6413#issuecomment-116590949
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/6976#issuecomment-116590950
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 zsxwing commented on the pull request:
https://github.com/apache/spark/pull/7071#issuecomment-116609232
I wonder this issue may depend on environments.
I think it depends on the performance of CPU. My CPU is 2.7G i7.
`drawTaskAssignmentTimeline` is not very fast
Github user tomwhite commented on a diff in the pull request:
https://github.com/apache/spark/pull/7014#discussion_r33454364
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala ---
@@ -662,6 +662,7 @@ private[spark] class TaskSetManager(
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6982#issuecomment-116621677
[Test build #35979 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35979/console)
for PR 6982 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7083#issuecomment-116621661
[Test build #978 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/978/console)
for PR 7083 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6982#issuecomment-116621696
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 hhbyyh opened a pull request:
https://github.com/apache/spark/pull/7084
[Spark-8703] [ML] Add CountVectorizer as a ml transformer to convert
document to words count vector
jira: https://issues.apache.org/jira/browse/SPARK-8703
Converts a text document to a
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/7085#issuecomment-116703647
Not a python person here, but I suspect that is indeed a good fix.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6743#issuecomment-116707373
[Test build #35990 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35990/console)
for PR 6743 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6982#issuecomment-116731548
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/6982#issuecomment-116731509
[Test build #35987 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35987/console)
for PR 6982 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6830#issuecomment-116735294
[Test build #35992 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35992/consoleFull)
for PR 6830 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6977#issuecomment-116735212
@rxin, was this example intended to work?
---
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/7060#issuecomment-116735798
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/7060#issuecomment-116735845
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/6338#issuecomment-116735821
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/6743#issuecomment-116735809
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/6743#issuecomment-116735844
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/7060#issuecomment-116736531
[Test build #35993 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35993/consoleFull)
for PR 7060 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7085#issuecomment-116737653
[Test build #35986 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35986/console)
for PR 7085 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7082#issuecomment-116737691
[Test build #35985 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35985/console)
for PR 7082 at commit
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6262#discussion_r33477722
--- Diff: python/pyspark/tests.py ---
@@ -874,6 +874,15 @@ def
test_sortByKey_uses_all_partitions_not_only_first_and_last(self):
for size
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7085#issuecomment-116737714
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/7082
---
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 koertkuipers commented on the pull request:
https://github.com/apache/spark/pull/6361#issuecomment-116739363
@JoshRosen one issue i see with publishing a modified chill package: we
read files in spark that were written by scalding using chill/kryo for
serialization of
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6743#issuecomment-116705375
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 have
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7085#issuecomment-116723253
LGTM. I guess the problem in the old code was a precedence issue that was
causing the implicitly-concatenated string to be joined to each profile instead
of
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7087#issuecomment-116727897
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/7087#issuecomment-116728823
[Test build #35991 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35991/consoleFull)
for PR 7087 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7036#issuecomment-116731697
@srowen, the doc change looks fine to me, so I think we should merge this
now and revisit automatically adding the wildcard later.
---
If your project is set up for
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/6830#discussion_r33476214
--- Diff: python/run-tests ---
@@ -126,7 +126,20 @@ function run_streaming_tests() {
KAFKA_ASSEMBLY_JAR=$f
done
-export
Github user sun-rui commented on the pull request:
https://github.com/apache/spark/pull/6743#issuecomment-116734776
rebased
---
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 JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6830#discussion_r33477034
--- Diff: dev/sparktestsupport/modules.py ---
@@ -241,7 +250,7 @@ def contains_file(self, filename):
pyspark_core = Module(
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6338#issuecomment-116735857
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/6338#issuecomment-116736089
[Test build #35995 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35995/consoleFull)
for PR 6338 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7029#issuecomment-116736915
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/7029#issuecomment-116736971
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/7029#issuecomment-116737348
[Test build #35996 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35996/consoleFull)
for PR 7029 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6743#issuecomment-116707411
Build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6982#issuecomment-116720487
[Test build #35984 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35984/console)
for PR 6982 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7087#issuecomment-116727918
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6361#issuecomment-116730892
@koertkuipers, I have a few comments about Chill on the JIRA ticket. If
necessary, we can consider publishing our own modified Chill package under the
Spark
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6830#issuecomment-116733372
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/6830#issuecomment-116733274
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6917#issuecomment-116732944
I think that we should put this on hold for now and revisit after we've
refactored the Jenkins triggering script so that we can explicitly tell Jenkins
whether to run
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6338#issuecomment-116735309
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
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/6830#discussion_r33477782
--- Diff: dev/sparktestsupport/modules.py ---
@@ -241,7 +250,7 @@ def contains_file(self, filename):
pyspark_core = Module(
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7082#issuecomment-116737751
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/5250#issuecomment-116704879
@tigerquoll would you mind closing this PR then? others can't close it
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6743#issuecomment-116706613
[Test build #35990 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35990/consoleFull)
for PR 6743 at commit
Github user sun-rui commented on the pull request:
https://github.com/apache/spark/pull/6743#issuecomment-116710169
Add support for shipping SparkR package for R workers required by RDD APIs.
Tested createDataFrame() by creating a DataFrame from an R list.
Remove sparkRLibDir
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6982#issuecomment-116720529
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/6338#issuecomment-116735485
The error message from AMPLab Jenkins is due to a problem in our Jenkins
configuration, not a problem in tests. Let me run this again and I'll merge
once SparkQA says
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/3234#issuecomment-116739058
Hey @ankurdave, it looks like this PR has gone stale, so do you mind
closing it for now and re-opening it once you're ready to work on it again?
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6743#issuecomment-116705414
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 this
Github user stevencanopy commented on the pull request:
https://github.com/apache/spark/pull/7048#issuecomment-116718717
Thanks @liancheng for looking into the Parquet spec! Yes, I first
encountered the bug when I was converting Avro to Parquet with parquet-mr 1.7.0.
I've
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/7087
[SPARK-8680][SQL] Slightly improve PropagateTypes
JIRA: https://issues.apache.org/jira/browse/SPARK-8680
You can merge this pull request into a Git repository by running:
$ git pull
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/6830#discussion_r33476124
--- Diff: dev/sparktestsupport/modules.py ---
@@ -241,7 +250,7 @@ def contains_file(self, filename):
pyspark_core = Module(
Github user thegiive commented on the pull request:
https://github.com/apache/spark/pull/7006#issuecomment-116732542
Hi, is there anyone who can confirm this patch? @andrewor14 or someone else
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6743#issuecomment-116736423
[Test build #35994 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35994/consoleFull)
for PR 6743 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6830#issuecomment-116739412
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/6830#issuecomment-116739442
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/6743#issuecomment-116739769
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/6743#issuecomment-116739746
[Test build #35994 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35994/console)
for PR 6743 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6830#issuecomment-116741414
Oh, that failure is due to a doctest canary test that I added to
`dev/run-tests.py`:
```
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7077#issuecomment-116742573
Jenkins, this is ok to test.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6947
---
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 zsxwing opened a pull request:
https://github.com/apache/spark/pull/7088
[SPARK-8705][WebUI]Don't display rects when totalExecutionTime is 0
Because `System.currentTimeMillis()` is not accurate for tasks that only
need several milliseconds, sometimes
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/7088#issuecomment-116751759
/cc @sarutak
---
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7058#issuecomment-116751724
LGTM. I used `pylint` / `prospector` to lint this file and it looks like
this has fixed all occurrences of the dangerous-default-value pattern in this
file.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7088#issuecomment-116754818
[Test build #36000 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36000/consoleFull)
for PR 7088 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7077#issuecomment-116761721
[Test build #35999 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35999/consoleFull)
for PR 7077 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7077#issuecomment-116761771
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 dragos commented on the pull request:
https://github.com/apache/spark/pull/5563#issuecomment-116740081
This doesn't work with scalar attributes. For example:
```
mesos-slave --master=aquarius:5050 --attributes=zone:main;color:3
```
and then
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7020#issuecomment-116741027
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/7085
---
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/7020#issuecomment-116740988
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 coolfrood commented on the pull request:
https://github.com/apache/spark/pull/6361#issuecomment-116741038
I think the serialization format should be the same with a minor version
bump.
How hard would it be to get Chill updated to use a newer version (2.24) of
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6830#issuecomment-116740310
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7077#issuecomment-116743021
LGTM, since this is consistent with how we handle other errors in
`CoarseGrainedExecutorBackend`.
---
If your project is set up for it, you can reply to this email
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7077#issuecomment-116744660
[Test build #35999 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35999/consoleFull)
for PR 7077 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6947#issuecomment-116749219
Great; merging to master.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4229#issuecomment-116753570
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/4229#issuecomment-116754160
[Test build #36001 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36001/consoleFull)
for PR 4229 at commit
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/5423#discussion_r33484523
--- Diff: docs/monitoring.md ---
@@ -256,6 +256,157 @@ still required, though there is only one application
available. Eg. to see the
running app, you
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6338#issuecomment-116757645
Actually, I have one concern about exception masking; will comment inline.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/5423#discussion_r33484808
--- Diff:
yarn/history/src/main/scala/org/apache/spark/deploy/history/yarn/YarnHistoryProvider.scala
---
@@ -0,0 +1,1015 @@
+/*
+ * Licensed to the
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/5423#discussion_r33485047
--- Diff:
yarn/history/src/main/scala/org/apache/spark/deploy/history/yarn/YarnHistoryProvider.scala
---
@@ -0,0 +1,1015 @@
+/*
+ * Licensed to the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6830#issuecomment-116758518
[Test build #36002 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36002/consoleFull)
for PR 6830 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7058#issuecomment-116759482
[Test build #36003 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36003/consoleFull)
for PR 7058 at commit
Github user MechCoder commented on the pull request:
https://github.com/apache/spark/pull/7058#issuecomment-116759456
I pushed one more instance that I came across today. Btw, what's with the
comment showing test failed but the build showing test passed.
---
If your project is set
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6338#issuecomment-116759535
Also, /cc @davies for another pair of eyes. This seems to match up with
the example at https://docs.python.org/2/library/socket.html#example, so it
seems okay, but I
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/5423#discussion_r33485556
--- Diff:
yarn/history/src/main/scala/org/apache/spark/deploy/history/yarn/YarnHistoryProvider.scala
---
@@ -0,0 +1,1015 @@
+/*
+ * Licensed to the
Github user steveloughran commented on a diff in the pull request:
https://github.com/apache/spark/pull/5423#discussion_r33486012
--- Diff:
yarn/history/src/main/scala/org/apache/spark/deploy/history/yarn/YarnEventListener.scala
---
@@ -0,0 +1,133 @@
+/*
+ * Licensed to
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/7026#discussion_r33486250
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/client/package.scala ---
@@ -32,13 +32,36 @@ package object client {
// Hive 0.14 depends
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/7052#issuecomment-116762807
This patch adds the following public classes (experimental):
Most of those are package-private, seems like the script needs some
tweaking.
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7058#issuecomment-116762732
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/7058#issuecomment-116762717
[Test build #36003 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36003/console)
for PR 7058 at commit
101 - 200 of 1332 matches
Mail list logo
