Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/5841
---
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/5841#issuecomment-108125497
[Test build #34019 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34019/consoleFull)
for PR 5841 at commit
[`2821481`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5841#issuecomment-108125511
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/5841#issuecomment-108093194
[Test build #34019 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34019/consoleFull)
for PR 5841 at commit
[`2821481`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5841#issuecomment-108092971
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/5841#issuecomment-108093008
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/5841#issuecomment-108092332
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5841#issuecomment-108043870
**[Test build #33996 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33996/consoleFull)**
for PR 5841 at commit
[`2821481`](https://gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5841#issuecomment-108043914
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/5841#issuecomment-108023643
LGTM after a read through the changes. I understand the intent and it makes
sense. I haven't tested it myself.
---
If your project is set up for it, you can reply to thi
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/5841#issuecomment-107996878
Ok, last patch LGTM. I wonder if it's worth it to add `KILLED` to the
condition here:
https://github.com/apache/spark/blob/master/yarn/src/main/scala/org/apache/spark/dep
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5841#issuecomment-107998131
[Test build #33996 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33996/consoleFull)
for PR 5841 at commit
[`2821481`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5841#issuecomment-107997533
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/5841#issuecomment-107997557
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/5841#issuecomment-98239407
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/315
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5841#issuecomment-98239404
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/5841#issuecomment-98239392
[Test build #31582 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31582/consoleFull)
for PR 5841 at commit
[`bf139b5`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5841#issuecomment-98204566
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/5841#issuecomment-98204666
[Test build #31582 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31582/consoleFull)
for PR 5841 at commit
[`bf139b5`](https://githu
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5841#issuecomment-98204539
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 ha
GitHub user vanzin opened a pull request:
https://github.com/apache/spark/pull/5841
[SPARK-6324] [core] Centralize handling of script usage messages.
Reorganize code so that the launcher library handles most of the work
of printing usage messages, instead of having an awkward pro
21 matches
Mail list logo
