Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15958
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15958
**[Test build #69395 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69395/consoleFull)**
for PR 15958 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15987
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69397/
Test PASSed.
---
Github user a-roberts commented on the issue:
https://github.com/apache/spark/pull/15736
Good point, done, I can get profiling the below code then? Builds fine and
no scalastyle problems
```
def getComparator[K](keyComparator: Option[Comparator[K]]):
Comparator[(Int,
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15987
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15987
**[Test build #69397 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69397/consoleFull)**
for PR 15987 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16079
**[Test build #69404 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69404/consoleFull)**
for PR 16079 at commit
GitHub user wangyum opened a pull request:
https://github.com/apache/spark/pull/16079
[SPARK-18645][Deploy] Fix spark-daemon.sh arguments error lead to throws
Unrecognized option
## What changes were proposed in this pull request?
spark-daemon.sh will lost single quotes
Github user a-roberts commented on the issue:
https://github.com/apache/spark/pull/15713
In response to @rxin's question, for HiBench CompactBuffers are **used only
on PageRank** (none of the other 11) and these buffers mainly have between 3
and 40 elements, no more than 60, never
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15736
Looks right except you just want to write
```
if (...) {
...
} else {
new Comparator...
}
```
---
If your project is set up for it, you can reply to this email
Github user a-roberts commented on the issue:
https://github.com/apache/spark/pull/15736
@srowen how about this for profiling?
```
private[spark] object WritablePartitionedPairCollection {
/**
* Takes an optional parameter (keyComparator), use if provided
Github user MLnick commented on the issue:
https://github.com/apache/spark/pull/16037
What worries me more actually is that the initial vector when sent in the
closure should be compressed. So why is this issue occurring? Is it a problem
with serialization / compression? OR even
Github user MLnick commented on the issue:
https://github.com/apache/spark/pull/16037
Right ok. So I think the approach of making the zero vector sparse then
calling `toDense` in `seqOp` as @srowen suggested makes most sense.
Currently the gradient vector *must* be dense in
Github user MLnick commented on the issue:
https://github.com/apache/spark/pull/16078
@AnthonyTruchet I think in this case it was just confusing to have many PRs
opened against the issue. One option is to either adjust the existing PR with
changes (so that only one PR is open).
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15979
**[Test build #69403 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69403/consoleFull)**
for PR 15979 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15671
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15671
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69400/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15671
**[Test build #69400 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69400/consoleFull)**
for PR 15671 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/15979
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 feature
enabled and wishes
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/11974
**[Test build #69402 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69402/consoleFull)**
for PR 11974 at commit
Github user AnthonyTruchet closed the pull request at:
https://github.com/apache/spark/pull/16078
---
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
Github user AnthonyTruchet commented on the issue:
https://github.com/apache/spark/pull/16078
In order to reduce the mess around multiple PRs I'll close this one and
rebase the change in #16037 as you requested.
What is the right way,convenient for you, to share a proposal
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15314
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15314
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69399/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/12896
**[Test build #69401 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69401/consoleFull)**
for PR 12896 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15314
**[Test build #69399 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69399/consoleFull)**
for PR 15314 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16037
This should be the main PR @MLnick
---
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
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16069
Regarding plugin updates: I wouldn't mind updating the Maven plugins too
while you're at it. `mvn versions:display-plugin-updates` will show you all the
candidates. Some changes we can't or won't
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16072
**[Test build #3445 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3445/consoleFull)**
for PR 16072 at commit
Github user MLnick commented on the issue:
https://github.com/apache/spark/pull/16037
This is all a bit confusing - can we highlight which PR is actually to be
reviewed?
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/16040
---
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 issue:
https://github.com/apache/spark/pull/15979
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15979
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69394/
Test FAILed.
---
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16040
Merged to master/2.1
---
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,
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15979
**[Test build #69394 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69394/consoleFull)**
for PR 15979 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16060
**[Test build #3446 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3446/consoleFull)**
for PR 16060 at commit
Github user ueshin commented on a diff in the pull request:
https://github.com/apache/spark/pull/15780#discussion_r90199899
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/ScalaReflection.scala
---
@@ -590,7 +591,11 @@ object ScalaReflection extends
Github user ueshin commented on a diff in the pull request:
https://github.com/apache/spark/pull/15780#discussion_r90199326
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/ScalaReflection.scala
---
@@ -590,7 +591,11 @@ object ScalaReflection extends
Github user AnthonyTruchet commented on the issue:
https://github.com/apache/spark/pull/16038
Agreed this is too ML specific to be deserve a fix in core.
---
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 AnthonyTruchet closed the pull request at:
https://github.com/apache/spark/pull/16038
---
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
Github user AnthonyTruchet commented on the issue:
https://github.com/apache/spark/pull/16078
It is necessary to address it in L-BFGS at least. We propose a solution in
core which can be legitimately rejected as not relevant for core. And two
solutions in MLlib, one provide for a
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/15817
---
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 MLnick commented on the issue:
https://github.com/apache/spark/pull/15817
Sorry for delay - this LGTM. Given it's been around for a while and given
RC2 is likely to be cut, I've gone ahead and merged to master / branch-2.1.
Thanks!
---
If your project is set up for it,
Github user ueshin commented on a diff in the pull request:
https://github.com/apache/spark/pull/15620#discussion_r90188857
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/conditionalExpressions.scala
---
@@ -64,19 +64,72 @@ case class
Github user ueshin commented on a diff in the pull request:
https://github.com/apache/spark/pull/15780#discussion_r90193978
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/ScalaReflection.scala
---
@@ -590,7 +591,11 @@ object ScalaReflection extends
Github user lshmouse commented on the issue:
https://github.com/apache/spark/pull/13706
@lianhuiwang
Just a feedback. With this patch, creating a MACRO throws the following
exception.
Any suggestion? I am trying to debug it.
```
16/11/30 16:59:18 INFO
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16037
Following https://github.com/apache/spark/pull/16038 I suggest this proceed
by making the zero value a sparse vector, and then making it dense in the seqOp
immediately.
---
If your project is set
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16038
As in https://github.com/apache/spark/pull/16078 I do not think we should
merge a change like this. Let's fix the problem directly in
https://github.com/apache/spark/pull/16037
---
If your project
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16078
This is getting a bit out of hand, with 6 pull requests now. To be clear, I
do not think we should merge this change. It's not necessary to address the
problem.
---
If your project is set up for
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15671
**[Test build #69400 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69400/consoleFull)**
for PR 15671 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/15780#discussion_r90192638
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/ScalaReflection.scala
---
@@ -590,7 +591,11 @@ object ScalaReflection extends
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15314
**[Test build #69399 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69399/consoleFull)**
for PR 15314 at commit
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/15780#discussion_r90192290
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/ScalaReflection.scala
---
@@ -590,7 +591,11 @@ object ScalaReflection extends
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16078
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
Github user vijoshi commented on the issue:
https://github.com/apache/spark/pull/15991
@tgravescs would like to have this in 2.0 along with the other improvement
that got accepted for backport (spark-18010). so would you consider allowing
this into 2.0 as well?
---
If your project
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/15620#discussion_r90191991
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/conditionalExpressions.scala
---
@@ -64,19 +64,72 @@ case class
Github user AnthonyTruchet commented on the issue:
https://github.com/apache/spark/pull/16038
@mridulm we don't know how to monitor the size of the serialize task. Sure
it would not 10MB due to all those zeros. But we nonetheless measure a
significant increase in performance and
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/15620#discussion_r90191951
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/conditionalExpressions.scala
---
@@ -64,19 +64,72 @@ case class
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/15780#discussion_r90191825
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/ScalaReflection.scala
---
@@ -590,7 +591,11 @@ object ScalaReflection extends
GitHub user AnthonyTruchet opened a pull request:
https://github.com/apache/spark/pull/16078
[SPARK-18471][MLLIB] Fix huge vectors of zero send in closure in L-BFGS
## What changes were proposed in this pull request?
Introduced util TreeAggregatorWithZeroGenerator and used
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/15915
Is there any update? @JoshRosen
---
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
Github user uncleGen commented on a diff in the pull request:
https://github.com/apache/spark/pull/16052#discussion_r90191359
--- Diff:
streaming/src/test/scala/org/apache/spark/streaming/StreamingContextSuite.scala
---
@@ -869,6 +891,31 @@ object TestReceiver {
val
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15671
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69398/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15671
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15671
**[Test build #69398 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69398/consoleFull)**
for PR 15671 at commit
Github user uncleGen commented on a diff in the pull request:
https://github.com/apache/spark/pull/16052#discussion_r90191009
--- Diff:
streaming/src/test/scala/org/apache/spark/streaming/StreamingContextSuite.scala
---
@@ -869,6 +891,31 @@ object TestReceiver {
val
Github user liancheng commented on the issue:
https://github.com/apache/spark/pull/15979
Good to merge pending Jenkins. 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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15671
**[Test build #69398 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69398/consoleFull)**
for PR 15671 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/15780#discussion_r90190203
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/encoders/ExpressionEncoderSuite.scala
---
@@ -338,6 +338,18 @@ class
Github user kapilsingh5050 commented on a diff in the pull request:
https://github.com/apache/spark/pull/15620#discussion_r90189958
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/conditionalExpressions.scala
---
@@ -64,19 +64,72 @@ case class
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/15780#discussion_r90189759
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/objects/objects.scala
---
@@ -405,13 +407,12 @@ case class
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/15780#discussion_r90189486
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/ScalaReflection.scala
---
@@ -590,7 +591,12 @@ object ScalaReflection extends
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/15780#discussion_r90189388
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/ScalaReflection.scala
---
@@ -590,7 +591,12 @@ object ScalaReflection extends
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/16052
@rxin OK, I will backport it to branch-2.0
---
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 issue:
https://github.com/apache/spark/pull/15987
**[Test build #69397 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69397/consoleFull)**
for PR 15987 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16067
**[Test build #69396 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69396/consoleFull)**
for PR 16067 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16067
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 feature
enabled and wishes
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15958
**[Test build #69395 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69395/consoleFull)**
for PR 15958 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15979
**[Test build #69394 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69394/consoleFull)**
for PR 15979 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/15979
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 feature
enabled and wishes
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/15620#discussion_r90185819
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/conditionalExpressions.scala
---
@@ -64,19 +64,72 @@ case class
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/15958
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 feature
enabled and wishes
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/15620#discussion_r90185627
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/conditionalExpressions.scala
---
@@ -64,19 +64,72 @@ case class
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/15620#discussion_r90185562
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/conditionalExpressions.scala
---
@@ -64,19 +64,72 @@ case class
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/15620#discussion_r90185362
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/conditionalExpressions.scala
---
@@ -64,19 +64,72 @@ case class
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16060
**[Test build #3446 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3446/consoleFull)**
for PR 16060 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16072
**[Test build #3445 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3445/consoleFull)**
for PR 16072 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16060
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69389/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16072
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69384/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16072
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15979
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69387/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16067
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69388/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15979
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15975
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69392/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16060
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16048
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69391/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15975
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15958
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15958
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69393/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16048
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
501 - 600 of 601 matches
Mail list logo
