Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10392
---
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 ena
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10392#issuecomment-167114552
Merged 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 have this featu
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10392#issuecomment-166646614
Eh, I don't think anyone wants flaky tests of course. Search JIRA. They get
improved by people improving them -- please have a go if you'd like to help.
---
If your pro
Github user pierre-borckmans commented on the pull request:
https://github.com/apache/spark/pull/10392#issuecomment-166645424
Thanks, good to know. Is there work planned on that matter? Or do you guys
just specialise in "seeing that it was a flaky test, just restart them" ? :)
---
If
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10392#issuecomment-166640491
Yes, flaky tests. There are so many, some really complex integration tests,
that unfortunately something fails half the time
---
If your project is set up for it, you c
Github user pierre-borckmans commented on the pull request:
https://github.com/apache/spark/pull/10392#issuecomment-166637885
@srowen Thanks. Just for my curiosity, the failing tests were completely
unrelated, right? Does that mean master was in an unstable state? Or are the
unit test
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10392#issuecomment-166624346
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 a
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10392#issuecomment-166605772
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10392#issuecomment-166605771
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10392#issuecomment-166605662
**[Test build #48186 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48186/consoleFull)**
for PR 10392 at commit
[`707ce5b`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10392#issuecomment-166583582
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10392#issuecomment-166583580
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10392#issuecomment-166583532
**[Test build #48184 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48184/consoleFull)**
for PR 10392 at commit
[`c316479`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10392#issuecomment-166573828
**[Test build #48186 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48186/consoleFull)**
for PR 10392 at commit
[`707ce5b`](https://gi
Github user pierre-borckmans commented on the pull request:
https://github.com/apache/spark/pull/10392#issuecomment-166572991
@srowen I fixed the scala style issues and the string interpolator.
---
If your project is set up for it, you can reply to this email and have your
reply appea
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10392#issuecomment-166571605
**[Test build #48184 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48184/consoleFull)**
for PR 10392 at commit
[`c316479`](https://gi
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10392#discussion_r48237938
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -2073,8 +2073,9 @@ class SparkContext(config: SparkConf) extends Logging
with Executo
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10392#issuecomment-166568589
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10392#issuecomment-166568584
**[Test build #48181 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48181/consoleFull)**
for PR 10392 at commit
[`6e21b23`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10392#issuecomment-166568588
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10392#issuecomment-166568388
**[Test build #48181 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48181/consoleFull)**
for PR 10392 at commit
[`6e21b23`](https://gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10392#issuecomment-166568253
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10392#issuecomment-166568251
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 projec
Github user pierre-borckmans commented on the pull request:
https://github.com/apache/spark/pull/10392#issuecomment-166565536
@srowen Agreed. I reverted my changes, and updated the warning message.
Thanks for your review.
---
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/10392#issuecomment-166411099
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10392#issuecomment-166411102
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10392#issuecomment-166411093
**[Test build #48126 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48126/consoleFull)**
for PR 10392 at commit
[`bace5b9`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10392#issuecomment-166410688
**[Test build #48126 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48126/consoleFull)**
for PR 10392 at commit
[`bace5b9`](https://gi
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/10392#issuecomment-166407388
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 this feature
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10392#discussion_r48133110
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -2072,14 +2072,15 @@ class SparkContext(config: SparkConf) extends
Logging with Execu
Github user pierre-borckmans commented on a diff in the pull request:
https://github.com/apache/spark/pull/10392#discussion_r48103410
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -2072,14 +2072,15 @@ class SparkContext(config: SparkConf) extends
Logging
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10392#discussion_r48101284
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -2072,14 +2072,15 @@ class SparkContext(config: SparkConf) extends
Logging with Execu
32 matches
Mail list logo
