Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7512#issuecomment-123902356
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/7512#issuecomment-123902258
[Test build #38110 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38110/console)
for PR 7512 at commit
[`e24991a`](https://github.
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/7512
---
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/7512#issuecomment-123902090
Merged 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 have
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/7512#issuecomment-123900952
LGTM. @vanzin I also think this is ready to merge.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If you
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7512#issuecomment-123900561
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/7512#issuecomment-123900468
[Test build #64 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SlowSparkPullRequestBuilder/64/console)
for PR 7512 at commit
[`e24991a`](https://github.co
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7512#issuecomment-123863724
[Test build #38110 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38110/consoleFull)
for PR 7512 at commit
[`e24991a`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7512#issuecomment-123862445
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/7512#issuecomment-123862525
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/7512#issuecomment-123861945
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/7512#issuecomment-123862085
[Test build #64 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SlowSparkPullRequestBuilder/64/consoleFull)
for PR 7512 at commit
[`e24991a`](https://github
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7512#issuecomment-123861921
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/7512#issuecomment-123861378
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/7512#issuecomment-123861330
@JoshRosen any idea why this test keeps failing? Doesn't seem in any way
related to the change here. Wonder if other PRs are also flaky.
---
If your project is set up fo
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7512#issuecomment-123860605
[Test build #38103 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38103/console)
for PR 7512 at commit
[`e24991a`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7512#issuecomment-123860722
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/7512#issuecomment-123828034
[Test build #38103 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38103/consoleFull)
for PR 7512 at commit
[`e24991a`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7512#issuecomment-123827181
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/7512#issuecomment-123827135
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 sarutak commented on the pull request:
https://github.com/apache/spark/pull/7512#issuecomment-123825996
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 fe
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/7512#issuecomment-123794825
Wow builds are really flaky.
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 a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7512#issuecomment-123559491
**[Test build #38007 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38007/console)**
for PR 7512 at commit
[`e24991a`](https://github
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7512#issuecomment-123559499
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/7512#issuecomment-123525589
[Test build #38007 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38007/consoleFull)
for PR 7512 at commit
[`e24991a`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7512#issuecomment-123525485
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/7512#issuecomment-123525477
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 sarutak commented on the pull request:
https://github.com/apache/spark/pull/7512#issuecomment-123524996
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 fe
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/7512#issuecomment-123524521
I think, these failures are caused by flaky tests.
retest this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear o
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7512#issuecomment-123524231
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/7512#issuecomment-123524204
[Test build #37995 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37995/console)
for PR 7512 at commit
[`e24991a`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7512#issuecomment-123523193
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/7512#issuecomment-123523130
[Test build #45 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SlowSparkPullRequestBuilder/45/console)
for PR 7512 at commit
[`e24991a`](https://github.co
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7512#issuecomment-123506314
[Test build #37995 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37995/consoleFull)
for PR 7512 at commit
[`e24991a`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7512#issuecomment-123506244
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/7512#issuecomment-123506267
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/7512#issuecomment-123506084
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/7512#issuecomment-123506158
[Test build #45 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SlowSparkPullRequestBuilder/45/consoleFull)
for PR 7512 at commit
[`e24991a`](https://github
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7512#issuecomment-123506123
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/7512#issuecomment-123506106
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/7512#issuecomment-123473214
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/7512#issuecomment-123473171
[Test build #37972 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37972/console)
for PR 7512 at commit
[`e24991a`](https://github.
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/7512#issuecomment-123445452
LGTM pending tests (which shouldn't have a problem passing).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as wel
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7512#issuecomment-123436316
[Test build #37972 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37972/consoleFull)
for PR 7512 at commit
[`e24991a`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7512#issuecomment-123434675
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/7512#issuecomment-123434648
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 sarutak commented on the pull request:
https://github.com/apache/spark/pull/7512#issuecomment-123432813
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
en
Github user kmaehashi commented on a diff in the pull request:
https://github.com/apache/spark/pull/7512#discussion_r35132078
--- Diff:
repl/scala-2.10/src/main/scala/org/apache/spark/repl/SparkILoop.scala ---
@@ -1008,7 +1008,7 @@ class SparkILoop(
val jars = SparkILoop.g
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/7512#discussion_r35130006
--- Diff:
repl/scala-2.10/src/main/scala/org/apache/spark/repl/SparkILoop.scala ---
@@ -1008,7 +1008,7 @@ class SparkILoop(
val jars = SparkILoop.getA
Github user kmaehashi commented on a diff in the pull request:
https://github.com/apache/spark/pull/7512#discussion_r35129656
--- Diff:
repl/scala-2.10/src/main/scala/org/apache/spark/repl/SparkILoop.scala ---
@@ -1008,7 +1008,7 @@ class SparkILoop(
val jars = SparkILoop.g
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/7512#discussion_r35128003
--- Diff:
repl/scala-2.10/src/main/scala/org/apache/spark/repl/SparkILoop.scala ---
@@ -1008,7 +1008,7 @@ class SparkILoop(
val jars = SparkILoop.getA
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/7512#issuecomment-123238225
You're probably right. This makes sense if so. I'd still like to get more
knowledgeable eyes on it, from @sryza or @vanzin for example.
---
If your project is set up for
Github user kmaehashi commented on the pull request:
https://github.com/apache/spark/pull/7512#issuecomment-123203221
@srowen
```
OptionAssigner(args.name, YARN, CLUSTER, clOption = "--name"),
```
This is a different thing. This `--name` is an argument to the
`org
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7512#issuecomment-122671250
Can one of the admins verify this patch?
---
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 pr
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7512#issuecomment-122671107
Can one of the admins verify this patch?
---
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 pr
GitHub user kmaehashi opened a pull request:
https://github.com/apache/spark/pull/7512
[SPARK-9180] fix spark-shell to accept --name option
This patch fixes
[[SPARK-9180]](https://issues.apache.org/jira/browse/SPARK-9180).
Users can now set the app name of spark-shell using `spa
56 matches
Mail list logo
