Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7061#issuecomment-116182301
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7061#issuecomment-116182295
[Test build #35907 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35907/console)
for PR 7061 at commit
[`70eccbe`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7054#issuecomment-116181928
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7054#issuecomment-116181923
[Test build #35906 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35906/console)
for PR 7054 at commit
[`bfda9c4`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7062#issuecomment-116181720
[Test build #35911 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35911/consoleFull)
for PR 7062 at commit
[`c088b72`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7062#issuecomment-116181663
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/7062#issuecomment-116181658
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 h
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/7062#issuecomment-116181569
cc @yhuai @JoshRosen
---
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 thi
GitHub user liancheng opened a pull request:
https://github.com/apache/spark/pull/7062
[SPARK-7845] [BUILD] Bumping default Hadoop version used in profile
hadoop-1 to 1.2.1
PR #5694 reverted PR #6384 while refactoring `dev/run-tests` to
`dev/run-tests.py`. Also, PR #6384 didn't bum
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6936#issuecomment-116181511
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6936#issuecomment-116181505
[Test build #35905 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35905/console)
for PR 6936 at commit
[`870338b`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7003#issuecomment-116180623
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7003#issuecomment-116180573
[Test build #35908 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35908/console)
for PR 7003 at commit
[`87b13cf`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7003#issuecomment-116177420
**[Test build #35903 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35903/console)**
for PR 7003 at commit
[`d2ebd72`](https://github
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7003#issuecomment-116177479
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7004#issuecomment-116174233
[Test build #35910 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35910/consoleFull)
for PR 7004 at commit
[`f4ae251`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7004#issuecomment-116173510
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/7004#issuecomment-116173506
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 h
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7004#issuecomment-116173172
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 h
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6967#issuecomment-116172735
[Test build #35909 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35909/consoleFull)
for PR 6967 at commit
[`f578d6d`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6967#issuecomment-116172515
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6967#issuecomment-116172518
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6967#issuecomment-116172419
Hopefully that test is just flaky, but let's see. If it fails again, I'll
investigate.
---
If your project is set up for it, you can reply to this email and have you
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6967#issuecomment-116172414
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 h
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6967#issuecomment-116172110
[Test build #35904 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35904/console)
for PR 6967 at commit
[`f578d6d`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6967#issuecomment-116172173
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7003#issuecomment-116166791
[Test build #35908 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35908/consoleFull)
for PR 7003 at commit
[`87b13cf`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7003#issuecomment-116166759
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7003#issuecomment-116166766
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7061#issuecomment-116165427
[Test build #35907 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35907/consoleFull)
for PR 7061 at commit
[`70eccbe`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7061#issuecomment-116165354
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/7061#issuecomment-116165349
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 h
Github user JDrit commented on the pull request:
https://github.com/apache/spark/pull/7004#issuecomment-116165233
This was intended to be a performance increase for spark-core with RDDs.
This works separately from spark-avro. I realize that dataframes could also be
used but the goal w
GitHub user JoshRosen opened a pull request:
https://github.com/apache/spark/pull/7061
[SPARK-8683] [SPARK] Depend on mockito-core instead of mockito-all
Spark's tests currently depend on `mockito-all`, which bundles Hamcrest and
Objenesis classes. Instead, it should depend on `mock
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7054#issuecomment-116164855
[Test build #35906 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35906/consoleFull)
for PR 7054 at commit
[`bfda9c4`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7054#issuecomment-116164800
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/7054#issuecomment-116164794
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 h
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7054#issuecomment-116164685
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 h
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7004#issuecomment-116164570
Also, to clarify: is this primarily intended to improve the performance of
programs written against the Spark Core API? For Spark SQL + DataFrames, I
think the [spark
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6936#issuecomment-116164424
[Test build #35905 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35905/consoleFull)
for PR 6936 at commit
[`870338b`](https://gith
Github user smartkiwi commented on the pull request:
https://github.com/apache/spark/pull/6936#issuecomment-116164420
Python doctests are rather limited in expressiveness, but efficient in
keeping examples bug free in documentation.
Anywhere - here is another patch that works in bo
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6936#issuecomment-116164301
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6936#issuecomment-116164305
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6967#issuecomment-116164101
[Test build #35904 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35904/consoleFull)
for PR 6967 at commit
[`f578d6d`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6967#issuecomment-116163919
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/6967#issuecomment-116163912
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 h
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6967#issuecomment-116163861
@davies, thanks for the review. I've addressed your two comments, so let's
wait and see if this passes tests. Once it passes, I'll merge and rebase my
other PRs.
--
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7060#issuecomment-116163783
[Test build #35899 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35899/console)
for PR 7060 at commit
[`d96da7e`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7060#issuecomment-116163791
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 project
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6936#issuecomment-116163462
Yeah, no rush; sorry for the hassle. At some point we should update the
contributing guide to include tips on this stuff, such as the doctest trick.
---
If your proj
Github user smartkiwi commented on the pull request:
https://github.com/apache/spark/pull/6936#issuecomment-116163405
Thanks for hints
Retesting locally with python3 and python2. I will push update in ~30
minutes
---
If your project is set up for it, you can reply to this email a
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7030#issuecomment-116163338
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7030#issuecomment-116163334
[Test build #35902 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35902/console)
for PR 7030 at commit
[`e3d7647`](https://github.
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/7026#discussion_r33417006
--- 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 o
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7004#issuecomment-116163279
Hey @JDrit,
Serialization performance is a big interest of mine and I'd be happy to
help with review of this patch. One question first, though: I've noticed th
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/7026#discussion_r33416949
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/client/VersionsSuite.scala ---
@@ -170,5 +180,12 @@ class VersionsSuite extends SparkFunSuite with L
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6952#issuecomment-116161226
Hey @jacek-lewandowski,
The change proposed here sounds reasonable, since spurious warnings/errors
during shutdown are really confusing to users. I'd be on-bo
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7036#issuecomment-116159934
Just curious: which filesystems does this hold true for? If there was some
way to detect whether we were using one of those filesystems, then we might be
able to log a
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/7030#issuecomment-116156846
Can we query the app name in cli or beeline? If so, I am wondering if we
can have a test for this change.
---
If your project is set up for it, you can reply to this emai
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/3794#issuecomment-116156525
In #7002, I added message processing time metrics to DAGScheduler using
Codahale metrics, so it should now be much easier to benchmark this.
---
If your project is se
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7003#issuecomment-116156176
[Test build #35903 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35903/consoleFull)
for PR 7003 at commit
[`d2ebd72`](https://gith
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7030#issuecomment-116154658
[Test build #35902 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35902/consoleFull)
for PR 7030 at commit
[`e3d7647`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7003#issuecomment-116153800
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/7003#issuecomment-116153642
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7030#issuecomment-116150307
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/7030#issuecomment-116150204
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 h
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/7030#issuecomment-116149665
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 this featur
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7003#issuecomment-116149512
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7003#issuecomment-116149511
[Test build #35901 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35901/console)
for PR 7003 at commit
[`bd4e99c`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7003#issuecomment-116149449
[Test build #35901 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35901/consoleFull)
for PR 7003 at commit
[`bd4e99c`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7003#issuecomment-116148941
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/7003#issuecomment-116148896
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 h
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/7023
---
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 enab
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7020#issuecomment-116148820
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7020#issuecomment-116148814
[Test build #35900 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35900/console)
for PR 7020 at commit
[`e70c312`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7020#issuecomment-116148270
[Test build #35900 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35900/consoleFull)
for PR 7020 at commit
[`e70c312`](https://gith
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7023#issuecomment-116148301
Alright, merging this to master + backport branches.
---
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6936#issuecomment-116148105
BTW, I think that you can get this to work with doctest.ELLIPSIS; the
problem is likely Python 2.x vs 3.x differences. You can fix this by using the
`ignore_unicode_p
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6936#discussion_r33416662
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -315,6 +315,14 @@ class SparkContext(config: SparkConf) extends Logging
with Execut
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7020#issuecomment-116147553
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/7020#issuecomment-116147548
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 h
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7020#issuecomment-116147483
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 h
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/7050
---
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 enab
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7050#issuecomment-116146384
Saw confirmation on JIRA that this patch fixes the issue, so I'm going to
merge to master.
---
If your project is set up for it, you can reply to this email and have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7060#issuecomment-116138794
[Test build #35899 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35899/consoleFull)
for PR 7060 at commit
[`d96da7e`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7060#issuecomment-116137780
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7060#issuecomment-116137825
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/7057#issuecomment-116137187
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7057#issuecomment-116137178
[Test build #35897 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35897/console)
for PR 7057 at commit
[`ad7820c`](https://github.
GitHub user brkyvz opened a pull request:
https://github.com/apache/spark/pull/7060
[SPARK-8681] fixed wrong ordering of columns in crosstab
I specifically randomized the test. What crosstab does is equivalent to a
countByKey, therefore if this test fails again for any reason, we wi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7059#issuecomment-116132999
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7059#issuecomment-116132934
[Test build #35895 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35895/console)
for PR 7059 at commit
[`f7b5308`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7058#issuecomment-116132214
[Test build #35898 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35898/console)
for PR 7058 at commit
[`95f7ff2`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7058#issuecomment-116132253
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7058#issuecomment-116122319
[Test build #35898 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35898/consoleFull)
for PR 7058 at commit
[`95f7ff2`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7058#issuecomment-116121945
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/7058#issuecomment-116121931
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 h
Github user MechCoder commented on the pull request:
https://github.com/apache/spark/pull/7058#issuecomment-116121669
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7058#issuecomment-116121626
[Test build #35896 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35896/console)
for PR 7058 at commit
[`95f7ff2`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7058#issuecomment-116121629
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 project
101 - 200 of 255 matches
Mail list logo
