Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2259#issuecomment-54704441
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19904/consoleFull)
for PR 2259 at commit
[`583716e`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2273#issuecomment-54704438
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19901/consoleFull)
for PR 2273 at commit
[`0e02379`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2264#issuecomment-54704437
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19902/consoleFull)
for PR 2264 at commit
[`c87355b`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2164#issuecomment-54704448
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19905/consoleFull)
for PR 2164 at commit
[`b035325`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2262#issuecomment-54704440
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19903/consoleFull)
for PR 2262 at commit
[`3e1b05c`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2294#issuecomment-54704308
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19896/consoleFull)
for PR 2294 at commit
[`848406c`](https://github.com/a
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/2288#issuecomment-54704149
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 th
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/2259#issuecomment-54704111
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 th
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/2292#issuecomment-54704106
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 th
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/1592#issuecomment-54704073
@marmbrus This seems that JListWrapper() can not be serialized by kryo
correctly, but I don't know how to reproduce it in Scala.
Reproduce this bug in one line Pyt
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2285#issuecomment-54703906
Can you change an old API to make sure this is reporting correctly?
---
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/2297
---
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 puravaggarwal commented on the pull request:
https://github.com/apache/spark/pull/89#issuecomment-54703862
As per discussions above - closing the pull request
---
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 puravaggarwal closed the pull request at:
https://github.com/apache/spark/pull/89
---
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 commented on the pull request:
https://github.com/apache/spark/pull/2297#issuecomment-54703849
Thanks. Merging in 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 have this
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2273#issuecomment-54703841
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 th
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/2226#issuecomment-54703827
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 feat
Github user rxin closed the pull request at:
https://github.com/apache/spark/pull/2247
---
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 enable
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2247#issuecomment-54703802
Ok I'm going to close this for now given the debate.
@mridulm it would be great to hear more about the performance difference.
It is hard for me to imagine a scenari
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2262#issuecomment-54703774
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 this
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2164#issuecomment-54703762
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 th
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2264#issuecomment-54703751
LGTM.
---
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
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2264#issuecomment-54703741
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 th
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2281#issuecomment-54703460
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19898/consoleFull)
for PR 2281 at commit
[`1ef7780`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2294#issuecomment-54703462
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19896/consoleFull)
for PR 2294 at commit
[`848406c`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2282#issuecomment-54703461
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19897/consoleFull)
for PR 2282 at commit
[`1de3f88`](https://github.com/ap
Github user staple commented on the pull request:
https://github.com/apache/spark/pull/1592#issuecomment-54703009
Sorry for the delay. I wrote a simple test case in pyspark to trigger the
kryo NPEs I've started seeing, that doesn't require my patch. I tested against
master at ba5bcadd
Github user ash211 commented on the pull request:
https://github.com/apache/spark/pull/1682#issuecomment-54702827
FWIW I run Spark in AWS and my ops team requires that all web interfaces
exposed through the proxy into the enclave have both SSL and user auth. Spark
doesn't support thos
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2282#issuecomment-54702660
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 th
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2281#issuecomment-54702644
That's a good idea to do. Need some performance profiling data though.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHu
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2281#issuecomment-54702649
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 th
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2279
---
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 aarondav commented on the pull request:
https://github.com/apache/spark/pull/2279#issuecomment-54702478
Merging into master. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not hav
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2279#issuecomment-54702433
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19891/consoleFull)
for PR 2279 at commit
[`14a720c`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2297#issuecomment-54702429
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19888/consoleFull)
for PR 2297 at commit
[`1e5ac9a`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2290#issuecomment-54702280
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19890/consoleFull)
for PR 2290 at commit
[`0c6d3bb`](https://github.com/a
Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/2279#issuecomment-54702259
Personally I'm happy with tests that succeed (proves that they ran). Feel
free to start a discussion on the mailing list about trimming down more,
though, of course.
Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/2279#issuecomment-54701700
Though more generally, it would be nice if we could trim the test output we
get. I wonder how much of it is actually valuable. For example, do we want to
print out lines
Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/2279#issuecomment-54701635
I'm totally fine with leaving the mountains in there. :mount_fuji:
Lemme know if I should close this PR.
---
If your project is set up for it, you can reply to
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/1723#issuecomment-54701548
Thanks @mubarak I will create a new PR and ask you to take a look.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHu
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1482#issuecomment-54701544
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19887/consoleFull)
for PR 1482 at commit
[`6673dca`](https://github.com/a
Github user mubarak commented on the pull request:
https://github.com/apache/spark/pull/1723#issuecomment-54701520
@tdas I don't mind. 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 tdas commented on the pull request:
https://github.com/apache/spark/pull/1723#issuecomment-54701514
@mubarak I commented earlier about me making some small refactoring. Do you
mind? See earlier comment.
---
If your project is set up for it, you can reply to this email and
Github user mubarak commented on the pull request:
https://github.com/apache/spark/pull/1723#issuecomment-54701499
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 have
Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/2279#issuecomment-54701501
I dunno, the mountain of pounds makes for an enjoyable scrolling experience.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2125#issuecomment-54701490
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19886/consoleFull)
for PR 2125 at commit
[`42c192a`](https://github.com/a
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/2078#issuecomment-54701484
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 mubarak commented on the pull request:
https://github.com/apache/spark/pull/1723#issuecomment-54701472
@tdas
+1. Can you please review? Thanks
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your proje
Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/2279#issuecomment-54701470
Compare [no
pounds](https://amplab.cs.berkeley.edu/jenkins/view/Pull%20Request%20Builders/job/SparkPullRequestBuilder/19891/consoleFull)
(from this PR) to [mountains of
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1106#issuecomment-54701392
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19892/consoleFull)
for PR 1106 at commit
[`bc91bb1`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2279#issuecomment-54701376
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19891/consoleFull)
for PR 2279 at commit
[`14a720c`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2294#issuecomment-54701390
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19889/consoleFull)
for PR 2294 at commit
[`56d7c85`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2297#issuecomment-54701362
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19888/consoleFull)
for PR 2297 at commit
[`1e5ac9a`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1106#issuecomment-54701368
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19892/consoleFull)
for PR 1106 at commit
[`bc91bb1`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2290#issuecomment-54701358
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19890/consoleFull)
for PR 2290 at commit
[`0c6d3bb`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2294#issuecomment-54701366
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19889/consoleFull)
for PR 2294 at commit
[`56d7c85`](https://github.com/ap
Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/1120#issuecomment-54701348
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 hav
Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/2281#issuecomment-54701316
If we anticipate turning sort shuffle on by default, should we consider
removing the non-copy approach? What performance impact do we expect?
---
If your project is set
Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/2290#issuecomment-54701298
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 hav
Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/2279#issuecomment-54701305
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 hav
Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/2277#issuecomment-54701254
New PR is at #2297.
---
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 fe
GitHub user nchammas opened a pull request:
https://github.com/apache/spark/pull/2297
[SPARK-3361] Expand PEP 8 checks to include EC2 script and Python examples
This PR resolves
[SPARK-3361](https://issues.apache.org/jira/browse/SPARK-3361) by expanding the
PEP 8 checks to cover th
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2282#issuecomment-54701177
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19878/consoleFull)
for PR 2282 at commit
[`1de3f88`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2281#issuecomment-54701132
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19877/consoleFull)
for PR 2281 at commit
[`1ef7780`](https://github.com/a
Github user nchammas closed the pull request at:
https://github.com/apache/spark/pull/2277
---
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 en
Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/2277#issuecomment-54700892
Closing this PR to merge upstream changes and then reopen from a new
branch. Apologies.
---
If your project is set up for it, you can reply to this email and have your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/899#issuecomment-54700786
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19884/consoleFull)
for PR 899 at commit
[`b768fc6`](https://github.com/apa
Github user WangTaoTheTonic commented on the pull request:
https://github.com/apache/spark/pull/1106#issuecomment-54700647
To @JoshRosen , the pr title is already modified, so is the jira.
@andrewor14 i think keeping track the workers' resource is too complex. So
I choose worker to
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1657#issuecomment-54700643
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19881/consoleFull)
for PR 1657 at commit
[`d8a5a12`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1160#issuecomment-54700622
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19883/consoleFull)
for PR 1160 at commit
[`dc1f70a`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/472#issuecomment-54700517
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19885/consoleFull)
for PR 472 at commit
[`22273b8`](https://github.com/apa
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/1723#issuecomment-54700500
Hey @mubarak, @andrewor14 and I discussed this PR, and it would be cool use
this opportunity refactor a the callSite stuff a bit, and document this
callsite stuff (which is
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1723#issuecomment-54700379
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19880/consoleFull)
for PR 1723 at commit
[`ceb43da`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2294#issuecomment-54700361
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19875/consoleFull)
for PR 2294 at commit
[`41b2da3`](https://github.com/a
Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/2290#issuecomment-54700338
Jenkinz, 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 nchammas commented on the pull request:
https://github.com/apache/spark/pull/2279#issuecomment-54700342
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/1381#issuecomment-54700336
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19882/consoleFull)
for PR 1381 at commit
[`681c26e`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2257#issuecomment-54700294
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19879/consoleFull)
for PR 2257 at commit
[`add8416`](https://github.com/a
Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/1482#issuecomment-54700237
Could this suppress the OOM message from getting to the driver? I thought
there was special handling for these messages (error code). This could result
in "executor died
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1482#issuecomment-54700201
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19887/consoleFull)
for PR 1482 at commit
[`6673dca`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2125#issuecomment-54700205
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19886/consoleFull)
for PR 2125 at commit
[`42c192a`](https://github.com/ap
Github user zeodtr commented on the pull request:
https://github.com/apache/spark/pull/899#issuecomment-54700088
@andrewor14 @vanzin As I already mentioned in another comment, This won't
compile on Hadoop < 2.4. So I suggested another method, but currently I have
not enough knowledge
Github user bbejeck commented on the pull request:
https://github.com/apache/spark/pull/2227#issuecomment-54699846
I've made the changes for mocking out the environment variable in the test.
I'd like to move the code from forked master branch to a topic branch. If I
rebase and move
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/1482#issuecomment-54699558
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 ha
Github user witgo closed the pull request at:
https://github.com/apache/spark/pull/2056
---
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 enabl
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2035#issuecomment-54699447
**[Tests timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19872/consoleFull)**
after a configured wait of `120m`.
---
If your project i
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/2056#issuecomment-54699362
@witgo Thanks for looking into this bug, but I think this patch is not
necessary anymore. So mind closing this PR?
---
If your project is set up for it, you can reply to th
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/1658#issuecomment-54699324
Hey @kmader, just curious, did you think about this BinaryData object idea?
If you don't have time to do it, someone else can also pick up from where you
left off.
---
I
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2117
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2214#issuecomment-54699185
**[Tests timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19847/consoleFull)**
after a configured wait of `120m`.
---
If your project i
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2209#issuecomment-54699191
**[Tests timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19848/consoleFull)**
after a configured wait of `120m`.
---
If your project i
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2220#issuecomment-54699188
**[Tests timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19845/consoleFull)**
after a configured wait of `120m`.
---
If your project i
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2229#issuecomment-54699180
**[Tests timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19844/consoleFull)**
after a configured wait of `120m`.
---
If your project i
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/2117#issuecomment-54699175
Thanks Andrew -- merged this in.
---
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 jkbradley commented on the pull request:
https://github.com/apache/spark/pull/2125#issuecomment-54699127
Looks like other tests are failing. I might as well push one more tweak
(speedup tweak based on profiling).
---
If your project is set up for it, you can reply to thi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2277#issuecomment-54698982
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19876/consoleFull)
for PR 2277 at commit
[`6cb948b`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1160#issuecomment-54698950
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19883/consoleFull)
for PR 1160 at commit
[`dc1f70a`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1657#issuecomment-54698946
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19881/consoleFull)
for PR 1657 at commit
[`d8a5a12`](https://github.com/ap
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/899#issuecomment-54698949
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19884/consoleFull)
for PR 899 at commit
[`b768fc6`](https://github.com/apac
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2281#issuecomment-54698939
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19877/consoleFull)
for PR 2281 at commit
[`1ef7780`](https://github.com/ap
1 - 100 of 500 matches
Mail list logo
