Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-98279651
Ok, finally merging into master. This feature will be in the 1.4.0 release.
Thanks everyone.
---
If your project is set up for it, you can reply to this email and
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/3074
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-97290781
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/3074#issuecomment-97290769
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-97290814
[Test build #31223 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31223/consoleFull)
for PR 3074 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-97305716
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-97305710
[Test build #31223 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31223/consoleFull)
for PR 3074 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-97305714
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 hellertime commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-97288972
@andrewor14 hmm. I'll have a look. That Jenkins output is none too helpful
:)
---
If your project is set up for it, you can reply to this email and have your
reply
Github user hellertime commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-97299396
Ok got it. I had pulled out the construction of an ExecutorInfo to shorten
line lengths, and that cause the type inference to decide that I wanted the
mesos
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-97197224
[Test build #31157 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31157/consoleFull)
for PR 3074 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-97197249
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/3074#issuecomment-97197254
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-97200770
@hellertime Tests don't seem to compile.
---
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
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-97174820
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-97175225
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-97175479
[Test build #31157 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31157/consoleFull)
for PR 3074 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-97175273
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-97174923
Jenkins, ok to test and 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
Github user doctapp commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-96791733
@hellertime thanks for the info, didn't catch this wasn't pre-installed
with mesos.
---
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/3074#issuecomment-96795918
[Test build #721 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/721/consoleFull)
for PR 3074 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-96770128
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
Github user hellertime commented on a diff in the pull request:
https://github.com/apache/spark/pull/3074#discussion_r29096430
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackendUtil.scala
---
@@ -0,0 +1,117 @@
+/*
+ * Licensed to
Github user hellertime commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-96114471
@doctapp actually in that example Dockerfile, the implication was that the
container had been run with a flag such as `-v
/usr/local/lib:/host/usr/local/lib:ro`, so
Github user hellertime commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-96135280
@andrewor14 all good suggestions. I've captured them all in this round of
commits. I'm still not sold on the naming of the Util object. So I've left it
for now.
Github user hellertime commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-96135291
Jenkins. Make it so! Oh right...
---
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
Github user tnachen commented on a diff in the pull request:
https://github.com/apache/spark/pull/3074#discussion_r28991901
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackendUtil.scala
---
@@ -0,0 +1,117 @@
+/*
+ * Licensed to the
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/3074#discussion_r28477222
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackend.scala
---
@@ -148,13 +148,26 @@ private[spark] class
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/3074#discussion_r28477417
--- Diff: docs/running-on-mesos.md ---
@@ -167,6 +167,14 @@ acquire. By default, it will acquire *all* cores in
the cluster (that get offere
only
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/3074#discussion_r28477087
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackendUtil.scala
---
@@ -0,0 +1,117 @@
+/*
+ * Licensed to
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-93610107
@hellertime Functionality-wise this looks fine to me. The comments I left
are relatively minor, mostly to do with code style and clarifying comments. It
appears that
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/3074#discussion_r28477157
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackendUtil.scala
---
@@ -0,0 +1,117 @@
+/*
+ * Licensed to
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/3074#discussion_r28477204
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackend.scala
---
@@ -148,13 +148,26 @@ private[spark] class
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/3074#discussion_r28475865
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackend.scala
---
@@ -148,13 +148,26 @@ private[spark] class
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/3074#discussion_r28476625
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackendUtil.scala
---
@@ -0,0 +1,117 @@
+/*
+ * Licensed to
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/3074#discussion_r28475951
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackendUtil.scala
---
@@ -0,0 +1,117 @@
+/*
+ * Licensed to
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/3074#discussion_r28476388
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackendUtil.scala
---
@@ -0,0 +1,117 @@
+/*
+ * Licensed to
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/3074#discussion_r28476422
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackendUtil.scala
---
@@ -0,0 +1,117 @@
+/*
+ * Licensed to
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/3074#discussion_r28476440
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackendUtil.scala
---
@@ -0,0 +1,117 @@
+/*
+ * Licensed to
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/3074#discussion_r28476893
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackendUtil.scala
---
@@ -0,0 +1,117 @@
+/*
+ * Licensed to
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/3074#discussion_r28477321
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackendUtil.scala
---
@@ -0,0 +1,117 @@
+/*
+ * Licensed to
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/3074#discussion_r28477280
--- Diff: docker/spark-mesos/Dockerfile ---
@@ -0,0 +1,37 @@
+# This is an example Dockerfile for creating a Spark image which can be
+# references
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/3074#discussion_r28476817
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackendUtil.scala
---
@@ -0,0 +1,117 @@
+/*
+ * Licensed to
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/3074#discussion_r28476685
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackendUtil.scala
---
@@ -0,0 +1,117 @@
+/*
+ * Licensed to
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/3074#discussion_r28477334
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackendUtil.scala
---
@@ -0,0 +1,117 @@
+/*
+ * Licensed to
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/3074#discussion_r28477358
--- Diff: docs/running-on-mesos.md ---
@@ -167,6 +167,14 @@ acquire. By default, it will acquire *all* cores in
the cluster (that get offere
only
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/3074#discussion_r28477372
--- Diff: docs/running-on-mesos.md ---
@@ -211,6 +219,43 @@ See the [configuration page](configuration.html) for
information on Spark config
/td
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/3074#discussion_r28476531
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackendUtil.scala
---
@@ -0,0 +1,117 @@
+/*
+ * Licensed to
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/3074#discussion_r28476488
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackendUtil.scala
---
@@ -0,0 +1,117 @@
+/*
+ * Licensed to
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/3074#discussion_r28476966
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackendUtil.scala
---
@@ -0,0 +1,117 @@
+/*
+ * Licensed to
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/3074#discussion_r28477717
--- Diff: docs/running-on-mesos.md ---
@@ -167,6 +167,14 @@ acquire. By default, it will acquire *all* cores in
the cluster (that get offere
only
Github user doctapp commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-92905011
There's a typo in `docker/spark-mesos/Dockerfile` where `ENV
MESOS_NATIVE_JAVA_LIBRARY /host/usr/local/lib/libmesos.so` should be refering
to /usr/local/lib/libmesos.so
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-92441223
[Test build #30170 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30170/consoleFull)
for PR 3074 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-92441238
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user hellertime commented on a diff in the pull request:
https://github.com/apache/spark/pull/3074#discussion_r28239714
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackendUtil.scala
---
@@ -0,0 +1,117 @@
+/*
+ * Licensed to
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-92408362
[Test build #30170 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/30170/consoleFull)
for PR 3074 at commit
Github user tnachen commented on a diff in the pull request:
https://github.com/apache/spark/pull/3074#discussion_r27784679
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackendUtil.scala
---
@@ -0,0 +1,117 @@
+/*
+ * Licensed to the
Github user tnachen commented on a diff in the pull request:
https://github.com/apache/spark/pull/3074#discussion_r27784657
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackendUtil.scala
---
@@ -0,0 +1,117 @@
+/*
+ * Licensed to the
Github user tnachen commented on a diff in the pull request:
https://github.com/apache/spark/pull/3074#discussion_r27784642
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackendUtil.scala
---
@@ -0,0 +1,117 @@
+/*
+ * Licensed to the
Github user tnachen commented on a diff in the pull request:
https://github.com/apache/spark/pull/3074#discussion_r27784630
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackendUtil.scala
---
@@ -0,0 +1,117 @@
+/*
+ * Licensed to the
Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-89056297
@andrewor14 I think this is ready to go, can you review this?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user hellertime commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-87014181
@tnachen indeed, ready to go.
---
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
Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-86645305
@hellertime looks like this is ready to go? @pwendell @mateiz what else is
needed to merge this?
---
If your project is set up for it, you can reply to this email and
Github user hellertime commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-85229862
@tnachen I'm stumped at the moment. I've gone so far as to exclude the
explicit docker/spark-mesos/Dockerfile path, but it is still not excluded. I
had put this down
Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-85228145
@hellertime are you able to figure out the RAT problem?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-85232216
@hellertime how about just add the Apache license on the top of the
Dockerfile?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-85256109
[Test build #29037 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29037/consoleFull)
for PR 3074 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-85256117
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-85235696
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-85235864
[Test build #29036 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29036/consoleFull)
for PR 3074 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-85254916
[Test build #29036 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29036/consoleFull)
for PR 3074 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-85254932
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user hellertime commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-85233392
@tnachen stop making things sound so damn easy! ;)
---
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 hellertime commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-85235541
Jenkins make it so! Oh wait, I don't have permission to do that.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-85236622
[Test build #29037 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/29037/consoleFull)
for PR 3074 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-81968390
[Test build #28679 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28679/consoleFull)
for PR 3074 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-81968401
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-81968372
[Test build #28679 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28679/consoleFull)
for PR 3074 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-81964915
[Test build #28676 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28676/consoleFull)
for PR 3074 at commit
Github user hellertime commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-81964794
@pwendell @mateiz I'd like to lobby towards getting this merged into the
next release. I've been making use of this branch in my Mesos cluster, and I
know that it
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-81965912
[Test build #28677 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28677/consoleFull)
for PR 3074 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-81965894
[Test build #28677 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28677/consoleFull)
for PR 3074 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-81965916
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-81964887
[Test build #28676 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28676/consoleFull)
for PR 3074 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-81964917
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user hellertime commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-81967379
Is there a link to documentation on the syntax of apache rat exclude
expressions? I didn't see any docs on the website, other than a very light
overview and --help
Github user gurvindersingh commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-77517021
So it appears as this one is not getting into 1.3 release, as the voting is
going on for RC3 now. I would have loved to test it out with 1.3 release if
possible,
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-76720065
[Test build #28173 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28173/consoleFull)
for PR 3074 at commit
Github user hellertime commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-76720424
Odd. I explicitly have a line in .rat-excludes for the path which caused
the error. What gives?
---
If your project is set up for it, you can reply to this email and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-76720082
[Test build #28173 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28173/consoleFull)
for PR 3074 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-76720085
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-76515967
@mateiz @pwendell I'm hoping to also see this merged soon, what else is
needed here?
---
If your project is set up for it, you can reply to this email and have your
Github user rbraley commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-75894649
I would love to see this merged for 1.3 as well :). I am curious why there
should be a conceptual separation between the test docker images and production
docker images.
Github user gurvindersingh commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-74931493
will be nice to have this patch merged in for 1.3 release. As we plan to
use this feature with Mesos and Spark
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-74936971
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-74936955
[Test build #27687 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27687/consoleFull)
for PR 3074 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-74936967
[Test build #27687 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27687/consoleFull)
for PR 3074 at commit
Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-74940888
@mateiz where do you suggest putting this Dockerfile? I have a Dockerfile
that builds Spark from source that depends on the Mesos image here:
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-74951728
The docker folder is for test images, but it could be a good place for this
one. I'll let @pwendell comment on it.
Does Apache Mesos publish a base Docker image?
Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/3074#issuecomment-74956760
Mesosphere does publish a Mesos image on each release (mesosphere/mesos),
with the each version tagged.
We don't tag the latest release with the :latest tag, I could
1 - 100 of 155 matches
Mail list logo
