Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/7629
---
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-135867765
Ok I'm merging 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 fe
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-135200381
Great - looks good!
On Aug 26, 2015 3:53 PM, "Marcelo Vanzin" wrote:
> Yay!
>
> â
> Reply to this email directly or view it on GitHub
>
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-135199475
Yay!
---
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 an
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-135195710
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-135195709
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/7629#issuecomment-135195602
[Test build #41647 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41647/console)
for PR 7629 at commit
[`a2c7c59`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-135145694
[Test build #41647 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41647/consoleFull)
for PR 7629 at commit
[`a2c7c59`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-135145248
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/7629#issuecomment-135145221
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-135144862
K - I just sent a hotfix to up the timeout.
On Wed, Aug 26, 2015 at 9:51 AM, Marcelo Vanzin
wrote:
> I'm working on fixing the root cause of the ti
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-135144791
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-135105812
I'm working on fixing the root cause of the timeouts (running unnecessary
tests). If you think it would be beneficial to just bump the timeout right now,
please just send
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-135105365
I still don't understand - why not fix the issue in a separate PR, get this
passing and then merge this? It will then benefit the other PR's also that
are facing
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-135104616
> but this one seems to be timing out with certainty every time
Often, but not deterministically every time. It seems to time out as often
as any other PR that n
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-135103392
Okay then - I would do that separately, get this PR passing, then merge it.
It is not good to merge a PR that deterministically fails jenkins. Have we
done that i
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-135082936
> you will need to change the timeout in the code
Yes but I don't want to do that as part of this change, since they're
unrelated things. All tests have been pas
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134867614
Marcelo you will need to change the timeout in the code itself for it to
increase from 175
On Aug 25, 2015 11:24 PM, "UCB AMPLab" wrote:
> Test FAILed.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134854998
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134855001
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134854945
**[Test build #41584 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41584/console)**
for PR 7629 at commit
[`a2c7c59`](https://github
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134808150
[Test build #41584 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41584/consoleFull)
for PR 7629 at commit
[`a2c7c59`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134807503
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/7629#issuecomment-134807514
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134806716
I've seen the failing test fail in other PRs (and it has passed here
before)... let's try again just in case. retest this please
---
If your project is set up for it, yo
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134802969
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134802972
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134802758
[Test build #41574 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41574/console)
for PR 7629 at commit
[`a2c7c59`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134775148
[Test build #41574 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41574/consoleFull)
for PR 7629 at commit
[`a2c7c59`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134773995
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/7629#issuecomment-134773980
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/7629#issuecomment-134768411
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134768410
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/7629#issuecomment-134768278
[Test build #41559 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41559/console)
for PR 7629 at commit
[`d234399`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134733766
[Test build #41559 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41559/consoleFull)
for PR 7629 at commit
[`d234399`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134732814
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/7629#issuecomment-134732792
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134732350
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134731892
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134731891
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/7629#issuecomment-134731807
[Test build #41539 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41539/console)
for PR 7629 at commit
[`d234399`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134684939
[Test build #41539 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41539/consoleFull)
for PR 7629 at commit
[`d234399`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134683516
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134683604
No, it shouldn't affect the test runtime at all. And I get timeouts in lots
of PRs, not just this one.
---
If your project is set up for it, you can reply to this email
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134683541
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134683004
Does this PR increase test time in some way? Just wondering why this would
consistently timeout when others don't.
On Tue, Aug 25, 2015 at 10:43 AM, Marcelo
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134682606
175m is starting to look really low. the scala/java unit tests took 143m to
run. anyway, retest this please.
---
If your project is set up for it, you can reply to this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134462736
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134462733
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/7629#issuecomment-134462689
**[Test build #41492 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41492/console)**
for PR 7629 at commit
[`d234399`](https://github
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134423253
[Test build #41492 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41492/consoleFull)
for PR 7629 at commit
[`d234399`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134422493
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/7629#issuecomment-134422481
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134422382
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134422378
Yeah sounds good - might be good to let it run one more time just to be
sure it's not affecting jenkins somehow.
On Mon, Aug 24, 2015 at 4:40 PM, Marcelo Van
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134414895
Seems like all tests passed, no idea why jenkins thinks they timed out.
AFAICT, this is good to do. @pwendell ?
---
If your project is set up for it, you can rep
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134414533
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134414535
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134414470
**[Test build #41471 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41471/console)**
for PR 7629 at commit
[`d234399`](https://github
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134373522
[Test build #41471 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41471/consoleFull)
for PR 7629 at commit
[`d234399`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134372214
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/7629#issuecomment-134372240
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134372031
le sigh. retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134363737
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134363733
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/7629#issuecomment-134363565
**[Test build #41461 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41461/console)**
for PR 7629 at commit
[`d234399`](https://github
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134306201
[Test build #41461 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41461/consoleFull)
for PR 7629 at commit
[`d234399`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134304656
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/7629#issuecomment-134304697
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134303307
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 this feat
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-133568076
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/7629#issuecomment-133567986
[Test build #41378 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41378/console)
for PR 7629 at commit
[`d234399`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-133568084
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-133528879
[Test build #41378 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41378/consoleFull)
for PR 7629 at commit
[`d234399`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-133528449
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/7629#issuecomment-133528426
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/7629#issuecomment-132416917
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-132416914
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/7629#issuecomment-132416671
[Test build #41174 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41174/console)
for PR 7629 at commit
[`e3585ec`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-132388004
[Test build #41174 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41174/consoleFull)
for PR 7629 at commit
[`e3585ec`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-132387201
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/7629#issuecomment-132387187
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/7629#issuecomment-130961265
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/7629#issuecomment-130961197
[Test build #40835 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40835/console)
for PR 7629 at commit
[`b16818f`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-130911228
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-130913427
[Test build #40835 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40835/consoleFull)
for PR 7629 at commit
[`b16818f`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-130911271
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-130909945
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 this feat
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-130884394
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/7629#issuecomment-130884122
[Test build #40803 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40803/console)
for PR 7629 at commit
[`b16818f`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-130845959
[Test build #40803 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/40803/consoleFull)
for PR 7629 at commit
[`b16818f`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-130845355
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/7629#issuecomment-130845388
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-130844717
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 this feat
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-130828206
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-130826120
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-128099706
If you break out the individual builds, many of them have been fine until
the Hive 1.2.1 patch. The top level dashboard isn't that useful bcause if any
one of the ~5 su
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-128099276
Sure. But as the test history of this PR shows, builds have been in pretty
bad shape for a while. :-(
---
If your project is set up for it, you can reply to this email a
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-128098191
Hey guys - thanks this is a cool and useful change. One thing I was
wondering, do you think we could wait until our builds are in better shape to
merge this since it's
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-128096165
I'm into this. Flagging for @pwendell one more time just in case.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub a
1 - 100 of 255 matches
Mail list logo