Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14684
**[Test build #63914 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63914/consoleFull)**
for PR 14684 at commit
[`c05fc3e`](https://github.com/apache/spark/commit/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14688
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63920/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14688
**[Test build #63920 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63920/consoleFull)**
for PR 14688 at commit
[`d50990c`](https://github.com/apache/spark/commit/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14688
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 does not have this feature
e
GitHub user jagadeesanas2 opened a pull request:
https://github.com/apache/spark/pull/14688
[SPARK-17095] [Documentation] [Latex and Scala doc do not play nicely]
## What changes were proposed in this pull request?
In Latex, it is common to find "}}}" when closing several ex
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14688
**[Test build #63920 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63920/consoleFull)**
for PR 14688 at commit
[`d50990c`](https://github.com/apache/spark/commit/d
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/14620
---
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 andreweduffy commented on the issue:
https://github.com/apache/spark/pull/14671
Yeah benchmarking is definitely a great idea, as it is likely Spark will be
better than Parquet at filtering individual records, but I'm still not quite
understanding why this filter is any dif
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14687
**[Test build #63919 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63919/consoleFull)**
for PR 14687 at commit
[`a4c015d`](https://github.com/apache/spark/commit/a
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/14620
Merging to 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 this feature
enabled and w
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/14687
[SPARK-17107][SQL] Remove redundant pushdown rule for Union
## What changes were proposed in this pull request?
The `Optimizer` rules `PushThroughSetOperations` and `PushDownPredicate`
have
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14620
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63912/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14620
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 does not have this feature
e
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/14676#discussion_r75110862
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/ResolveInlineTables.scala
---
@@ -0,0 +1,109 @@
+/*
+ * Licensed to
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14620
**[Test build #63912 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63912/consoleFull)**
for PR 14620 at commit
[`11bcb1d`](https://github.com/apache/spark/commit/
Github user skonto commented on a diff in the pull request:
https://github.com/apache/spark/pull/14667#discussion_r75110761
--- Diff: docs/running-on-mesos.md ---
@@ -207,6 +207,16 @@ The scheduler will start executors round-robin on the
offers Mesos
gives it, but there are no
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/14676#discussion_r75110610
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/ResolveInlineTables.scala
---
@@ -0,0 +1,109 @@
+/*
+ * Licensed to
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14686
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 project does not have this feat
GitHub user zenglinxi0615 opened a pull request:
https://github.com/apache/spark/pull/14686
[SPARK-16253][SQL] make spark sql compatible with hive sql that usingâ¦
## What changes were proposed in this pull request?
make spark sql compatible with hive sql that using python
Github user phalodi closed the pull request at:
https://github.com/apache/spark/pull/14684
---
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 en
Github user phalodi commented on the issue:
https://github.com/apache/spark/pull/14684
@srowen ok so i close this PR as you suggested.
---
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 fea
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/14685#discussion_r75106052
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/subquery.scala ---
@@ -56,30 +44,29 @@ trait ExecSubqueryExpression extends SubqueryExpre
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14279
I will take another look tomorrow. Please feel free to take a look further
because it's almost complete I think.
---
If your project is set up for it, you can reply to this email and have your
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14279
**[Test build #63918 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63918/consoleFull)**
for PR 14279 at commit
[`4171a3c`](https://github.com/apache/spark/commit/4
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14279
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 does not have this feature
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14279
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63917/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14279
**[Test build #63917 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63917/consoleFull)**
for PR 14279 at commit
[`c4900de`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14685
**[Test build #63916 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63916/consoleFull)**
for PR 14685 at commit
[`d2bd26c`](https://github.com/apache/spark/commit/d
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14279
**[Test build #63917 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63917/consoleFull)**
for PR 14279 at commit
[`c4900de`](https://github.com/apache/spark/commit/c
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14279
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63915/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14279
**[Test build #63915 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63915/consoleFull)**
for PR 14279 at commit
[`8bcdd59`](https://github.com/apache/spark/commit/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14279
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 does not have this feature
e
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/14685
cc @davies (we discussed this in PR
https://github.com/apache/spark/pull/14548)
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14279
Let me please rebase as it is now different a lot.
---
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 t
GitHub user hvanhovell opened a pull request:
https://github.com/apache/spark/pull/14685
[SPARK-17106][SQL] Simplify the SubqueryExpression interface
## What changes were proposed in this pull request?
The current subquery expression interface contains a little bit of
technical
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14279
**[Test build #63915 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63915/consoleFull)**
for PR 14279 at commit
[`8bcdd59`](https://github.com/apache/spark/commit/8
Github user phalodi commented on the issue:
https://github.com/apache/spark/pull/14684
@srowen Yes you are right but SPARK-16966 is only for spark session but
while user creating the spark context then they must be give app name. i think
for both spark session and spark context the be
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14684
This is a duplicate of SPARK-16966, pretty much. I don't think this
behavior here should be changed. See the fix for SPARK-16966 and discussion for
more about the intended behavior.
---
If your pro
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14683
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 does not have this feature
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14683
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63913/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14683
**[Test build #63913 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63913/consoleFull)**
for PR 14683 at commit
[`8360c29`](https://github.com/apache/spark/commit/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14682
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 does not have this feature
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14682
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63911/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14682
**[Test build #63911 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63911/consoleFull)**
for PR 14682 at commit
[`f9a8c76`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14684
**[Test build #63914 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63914/consoleFull)**
for PR 14684 at commit
[`c05fc3e`](https://github.com/apache/spark/commit/c
GitHub user phalodi opened a pull request:
https://github.com/apache/spark/pull/14684
[SPARK-17105][CORE] App name will be random UUID while creating spark
context if it will â¦
## What changes were proposed in this pull request?
App name will be random UUID while creating
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/14620
LGTM - pending Jenkins.
---
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 wish
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14683
Hm, this does not look up to date with master. The original changes were
already merged, so I think this would just include your doc changes. Maybe
squash your commits, rebase on master?
---
If you
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14683
**[Test build #63913 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63913/consoleFull)**
for PR 14683 at commit
[`8360c29`](https://github.com/apache/spark/commit/8
Github user GraceH commented on the issue:
https://github.com/apache/spark/pull/14683
@srowen Here we go. please feel free to let me know your comments.
---
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 GraceH opened a pull request:
https://github.com/apache/spark/pull/14683
[SPARK-16968]Add additional options in jdbc when creating a new table
## What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
In the PR, we just
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14671
@andreweduffy @rxin Maybe I can go for the simple benchmark quickly (maybe
within this weekend) and open a PR to disable Parquet row-by-row filtering if
it makes sense and this can be the reason
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14620
**[Test build #63912 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63912/consoleFull)**
for PR 14620 at commit
[`11bcb1d`](https://github.com/apache/spark/commit/1
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14559
@GraceH yeah you'll need a new PR. You can open it vs the same JIRA since
these are fairly tightly related.
---
If your project is set up for it, you can reply to this email and have your
reply appe
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14650
Seems OK to me, to the limits of my understanding, and given the logic of
https://github.com/apache/spark/pull/14650#issuecomment-240057336
---
If your project is set up for it, you can reply to thi
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/14667#discussion_r75097036
--- Diff: docs/running-on-mesos.md ---
@@ -207,6 +207,16 @@ The scheduler will start executors round-robin on the
offers Mesos
gives it, but there are no
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/14643#discussion_r75096884
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/classification/ProbabilisticClassifier.scala
---
@@ -201,11 +201,18 @@ abstract class ProbabilisticClassif
Github user andreweduffy commented on the issue:
https://github.com/apache/spark/pull/14671
That is true, but currently all filters are being pushed down to row-by-row
anyway when not using the vectorized reader, so I'm unclear why the IN filter
is special
---
If your project is set
Github user GraceH commented on the issue:
https://github.com/apache/spark/pull/14559
Hi @srowen @rxin , sorry for late response. I have added the document part.
https://github.com/GraceH/spark/commit/8360c2911b70aa628f8edba593e3764d3b07ca55
Shall I raise a new PR?
---
If your pr
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14659
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63910/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14659
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 does not have this feature
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14659
**[Test build #63910 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63910/consoleFull)**
for PR 14659 at commit
[`ec6833d`](https://github.com/apache/spark/commit/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13950
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63909/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13950
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 does not have this feature
e
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14671
I mean, maybe we should disable the row-by-row one in Parquet with a proper
benchmark first before handling `In` here.
---
If your project is set up for it, you can reply to this email and have
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13950
**[Test build #63909 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63909/consoleFull)**
for PR 13950 at commit
[`624af2e`](https://github.com/apache/spark/commit/
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14671
Yea, that is all true. Actually, it would be okay just not to pass the
filter
[here](https://github.com/apache/spark/blob/abff92bfdc7d4c9d2308794f0350561fe0ceb4dd/sql/core/src/main/scala/org/apa
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13950
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 does not have this feature
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13950
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63907/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13950
**[Test build #63907 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63907/consoleFull)**
for PR 13950 at commit
[`035478d`](https://github.com/apache/spark/commit/
Github user andreweduffy commented on a diff in the pull request:
https://github.com/apache/spark/pull/14671#discussion_r75092317
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/datasources/parquet/ParquetFilterSuite.scala
---
@@ -369,7 +369,7 @@ class ParquetFilt
Github user andreweduffy commented on the issue:
https://github.com/apache/spark/pull/14671
Thanks for the comments guys! Had to search through some code, but I think
I understand the current state of things. Correct me if I'm wrong, but it seems
that record-by-record filtering only o
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/14620#discussion_r75091055
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/parser/ParserUtilsSuite.scala
---
@@ -61,5 +102,88 @@ class ParserUtilsSuite extends
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14279
Sure, 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 this feature
enabled and wishes so, or
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14524
OK, this sounds like it could be a good change. I'd like to ask @jkbradley
again in case there was a strong reason I'm missing to fix the seed by default.
Also CC @davies if possible to consider the
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/14679
Now I have put the stacktrace in the JIRA, sorry for that.
I didn't look into this, seems like the behavior of scala reflection
methods is different between scala 2.10 and 2.11. Anyway the
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14555
That's a good point, it's public now. I think I agree with you then, it's
fairly important to retain the validation there. It would also be inconsistent
to move it back, yes, because I see the other
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14682
**[Test build #63911 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63911/consoleFull)**
for PR 14682 at commit
[`f9a8c76`](https://github.com/apache/spark/commit/f
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14562
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63908/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14562
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 does not have this feature
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14562
**[Test build #63908 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63908/consoleFull)**
for PR 14562 at commit
[`5c8f324`](https://github.com/apache/spark/commit/
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/14682
[SPARK-17104][SQL] LogicalRelation.newInstance should follow the semantics
of MultiInstanceRelation
## What changes were proposed in this pull request?
Currently `LogicalRelation.newInstanc
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14562
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 does not have this feature
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14562
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63906/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14562
**[Test build #63906 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63906/consoleFull)**
for PR 14562 at commit
[`e50aece`](https://github.com/apache/spark/commit/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14679
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 does not have this feature
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14679
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63902/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14576
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 does not have this feature
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14679
**[Test build #63902 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63902/consoleFull)**
for PR 14679 at commit
[`c04084d`](https://github.com/apache/spark/commit/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14576
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63903/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14576
**[Test build #63903 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63903/consoleFull)**
for PR 14576 at commit
[`1b57b74`](https://github.com/apache/spark/commit/
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14551
I'd expect the Gaussians to move as a result of this change. I think it's
fair to simply modify the test to match the current output in this case.
---
If your project is set up for it, you can repl
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/14674#discussion_r75082040
--- Diff: core/src/main/scala/org/apache/spark/SecurityManager.scala ---
@@ -282,7 +282,9 @@ private[spark] class SecurityManager(sparkConf:
SparkConf)
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14680
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 does not have this feature
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14680
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63904/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14681
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 does not have this feature
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14680
**[Test build #63904 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63904/consoleFull)**
for PR 14680 at commit
[`133e5de`](https://github.com/apache/spark/commit/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14681
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63905/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14681
**[Test build #63905 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63905/consoleFull)**
for PR 14681 at commit
[`ccd211f`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14659
**[Test build #63910 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63910/consoleFull)**
for PR 14659 at commit
[`ec6833d`](https://github.com/apache/spark/commit/e
601 - 700 of 731 matches
Mail list logo
