Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13703
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60634/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13703
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/13703
**[Test build #60634 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60634/consoleFull)**
for PR 13703 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/13631
@cloud-fan no problem at all.
---
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
Github user adrian-wang commented on a diff in the pull request:
https://github.com/apache/spark/pull/13652#discussion_r67289086
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/util/DateTimeUtils.scala
---
@@ -851,6 +851,29 @@ object DateTimeUtils {
}
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13698
**[Test build #60635 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60635/consoleFull)**
for PR 13698 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13703
**[Test build #60634 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60634/consoleFull)**
for PR 13703 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13697
**[Test build #60633 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60633/consoleFull)**
for PR 13697 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/13631
hi @viirya , we are auditing the insertion behaviour of spark sql, and will
have an agreement this week. How about we revisit this PR after that?
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13703
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60632/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13703
**[Test build #60632 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60632/consoleFull)**
for PR 13703 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13703
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 cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/13663#discussion_r67288169
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/DataFrameComplexTypeSuite.scala ---
@@ -26,6 +26,38 @@ import
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13697
**[Test build #3116 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3116/consoleFull)**
for PR 13697 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13703
**[Test build #60632 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60632/consoleFull)**
for PR 13703 at commit
Github user tdas commented on the issue:
https://github.com/apache/spark/pull/13703
@zsxwing Can you please take a look.
---
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 tdas opened a pull request:
https://github.com/apache/spark/pull/13703
[SPARK-15981][Fixed bug and added tests
## What changes were proposed in this pull request?
- Fixed bug in Python API of DataStreamReader
- Reduced code duplication between
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/13663#discussion_r67288116
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/complexTypeCreator.scala
---
@@ -71,7 +71,8 @@ case class
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/13698
LGTM
---
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 sun-rui commented on a diff in the pull request:
https://github.com/apache/spark/pull/13684#discussion_r67287926
--- Diff: R/pkg/R/DataFrame.R ---
@@ -1856,10 +1856,11 @@ setMethod("where",
#' the subset of columns.
#'
#' @param x A SparkDataFrame.
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13700
**[Test build #3118 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3118/consoleFull)**
for PR 13700 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13700
**[Test build #3117 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3117/consoleFull)**
for PR 13700 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13702
**[Test build #60631 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60631/consoleFull)**
for PR 13702 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13684
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60629/
Test PASSed.
---
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/13684
Thank you, @shivaram and @sun-rui .
Now, it's ready for review again.
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13684
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/13684
**[Test build #60629 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60629/consoleFull)**
for PR 13684 at commit
GitHub user ueshin opened a pull request:
https://github.com/apache/spark/pull/13702
[SPARK-15980][SQL] Add PushPredicateThroughObjectConsumer rule to Optimizer.
## What changes were proposed in this pull request?
This pr adds `PushPredicateThroughObjectConsumer` rule to
Github user sun-rui commented on the issue:
https://github.com/apache/spark/pull/13635
@shivaram, I probably take a look at this tonight.
---
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 issue:
https://github.com/apache/spark/pull/13700
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60626/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13700
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/13700
**[Test build #60626 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60626/consoleFull)**
for PR 13700 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12836
---
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 shivaram commented on the issue:
https://github.com/apache/spark/pull/12836
Merging this to master and 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 feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13661
**[Test build #60630 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60630/consoleFull)**
for PR 13661 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13678
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/13561
---
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 cloud-fan commented on the issue:
https://github.com/apache/spark/pull/13678
thanks, merging to master/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 feature
enabled
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/10896
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/10896
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60624/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/10896
**[Test build #60624 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60624/consoleFull)**
for PR 10896 at commit
Github user yanboliang commented on the issue:
https://github.com/apache/spark/pull/13641
@MLnick I found you did not add ```@Since``` for all params definition, is
this as expectedï¼I think we should add them.
---
If your project is set up for it, you can reply to this email and
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13684
**[Test build #60629 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60629/consoleFull)**
for PR 13684 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/11863
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60622/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/11863
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/11863
**[Test build #60622 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60622/consoleFull)**
for PR 11863 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12836
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60621/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12836
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/12836
**[Test build #60621 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60621/consoleFull)**
for PR 12836 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/13640
LGTM
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/13701
**[Test build #60628 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60628/consoleFull)**
for PR 13701 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/13701
@yhuai I am not sure the row-group info is exposed. But I've manually
output the `totalRowCount` in `SpecificParquetRecordReaderBase` to check the
total number of rows this `RecordReader` will
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13701
**[Test build #60627 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60627/consoleFull)**
for PR 13701 at commit
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/13701
[SPARK-15639][SQL] Try to push down filter at RowGroups level for parquet
reader
## What changes were proposed in this pull request?
The base class `SpecificParquetRecordReaderBase` used
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13697
**[Test build #3116 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3116/consoleFull)**
for PR 13697 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13684
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/13684
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60625/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13684
**[Test build #60625 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60625/consoleFull)**
for PR 13684 at commit
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/13371
Yea. Since this one was closed by asfgit, I am not sure you can reopen it.
On Wed, Jun 15, 2016 at 7:39 PM -0700, "Liang-Chi Hsieh"
wrote:
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13684
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60623/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13684
**[Test build #60623 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60623/consoleFull)**
for PR 13684 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13684
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/13700
**[Test build #60626 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60626/consoleFull)**
for PR 13700 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/13700
https://github.com/apache/spark/pull/13696 is the original patch for master.
---
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 rxin commented on the issue:
https://github.com/apache/spark/pull/13696
See https://github.com/apache/spark/pull/13700
---
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 rxin opened a pull request:
https://github.com/apache/spark/pull/13700
[SPARK-15979][SQL] Rename various Parquet support classes (branch-2.0).
## What changes were proposed in this pull request?
This patch renames various Parquet support classes from CatalystAbc to
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13684
**[Test build #60625 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60625/consoleFull)**
for PR 13684 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/13474
Looks like it's not. I'm going to merge it in 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/10896
**[Test build #60624 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60624/consoleFull)**
for PR 10896 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/13474
Was this merged into 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 feature
enabled and wishes
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13691
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/13612
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/13694
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/11373
---
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 rxin commented on the issue:
https://github.com/apache/spark/pull/13691
Merging in master/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 feature
enabled and wishes
Github user lianhuiwang commented on the issue:
https://github.com/apache/spark/pull/3976
@dileep1236 Can you find pyspark.zip in SPARK_HOME/python/lib/?
---
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 rxin commented on the issue:
https://github.com/apache/spark/pull/13694
Merging in master/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 feature
enabled and wishes
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/13696
I merged this into master but there is a conflict in 2.0. Going to submit a
separate pr.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13696
---
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/13447
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60619/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13447
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/13447
**[Test build #60619 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60619/consoleFull)**
for PR 13447 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/13696
Merging in master/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 feature
enabled and wishes
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13699
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60620/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13699
**[Test build #60620 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60620/consoleFull)**
for PR 13699 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13699
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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/13676#discussion_r67281085
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveInspectors.scala ---
@@ -479,7 +354,287 @@ private[hive] trait HiveInspectors {
}
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13684
**[Test build #60623 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60623/consoleFull)**
for PR 13684 at commit
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/13684
Thank you, @sun-rui .
Now, this PR checks all parameters' type correctly.
---
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 lianhuiwang commented on the issue:
https://github.com/apache/spark/pull/13676
LGTM
---
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 dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/13684#discussion_r67280096
--- Diff: R/pkg/R/DataFrame.R ---
@@ -1869,14 +1871,22 @@ setMethod("where",
#' path <- "path/to/file.json"
#' df <- read.json(path)
#'
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/13371
@yhuai ok. Do you mean I need to create a new PR for this?
---
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 yangw1234 commented on the issue:
https://github.com/apache/spark/pull/11929
Hi @hvanhovell , just checked. In branch-1.6 latest code, yes this problem
still exists. Branch master and branch-2.0 don't have this problem.
---
If your project is set up for it, you can reply
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/12836
**[Test build #60621 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60621/consoleFull)**
for PR 12836 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/11863
**[Test build #60622 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60622/consoleFull)**
for PR 11863 at commit
Github user koeninger commented on the issue:
https://github.com/apache/spark/pull/11863
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 this feature
enabled and
Github user lianhuiwang commented on a diff in the pull request:
https://github.com/apache/spark/pull/13676#discussion_r67277135
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveInspectors.scala ---
@@ -479,7 +354,287 @@ private[hive] trait HiveInspectors {
}
Github user koeninger commented on the issue:
https://github.com/apache/spark/pull/11863
Jenkins, retest this please
On Jun 15, 2016 8:43 PM, "UCB AMPLab" wrote:
> Merged build finished. Test FAILed.
>
> â
> You are receiving this
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13698
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/13698
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60618/
Test PASSed.
---
1 - 100 of 789 matches
Mail list logo