Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15708
Merging in 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 project does not have this feature
enabled and wishes so, or
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15707
**[Test build #3384 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3384/consoleFull)**
for PR 15707 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15702
**[Test build #67866 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67866/consoleFull)**
for PR 15702 at commit
GitHub user HyukjinKwon opened a pull request:
https://github.com/apache/spark/pull/15709
[SPARK-18190][Build][SparkR] Fix R version to not the latest in AppVeyor
## What changes were proposed in this pull request?
Currently, Spark supports the test on Windows via AppVeyor
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15707
**[Test build #3386 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3386/consoleFull)**
for PR 15707 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15707
**[Test build #67865 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67865/consoleFull)**
for PR 15707 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15626
**[Test build #67845 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67845/consoleFull)**
for PR 15626 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15704
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67857/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15704
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15709
Maybe, I might create a JIRA to describe the known issues with AppVeyor.
(does it make sense?)
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/15704#discussion_r85873381
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveExternalCatalog.scala ---
@@ -631,6 +631,42 @@ private[spark] class HiveExternalCatalog(conf:
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15688
**[Test build #67871 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67871/consoleFull)**
for PR 15688 at commit
Github user ericl commented on a diff in the pull request:
https://github.com/apache/spark/pull/15705#discussion_r85875944
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/CatalogFileIndex.scala
---
@@ -67,7 +67,10 @@ class CatalogFileIndex(
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15710
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/15710
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67872/
Test FAILed.
---
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/15710#discussion_r85878038
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/InsertIntoHadoopFsRelationCommand.scala
---
@@ -84,17 +84,22 @@ case class
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15705
**[Test build #67846 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67846/consoleFull)**
for PR 15705 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15705
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67846/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15705
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/15626
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 the issue:
https://github.com/apache/spark/pull/15706
This guy @transient must get a lot of emails ...
---
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 commented on the issue:
https://github.com/apache/spark/pull/15706
Can you change the title to "[SQL]" rather than "[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 does not have
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15707
**[Test build #67855 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67855/consoleFull)**
for PR 15707 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15708
**[Test build #67854 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67854/consoleFull)**
for PR 15708 at commit
GitHub user ericl opened a pull request:
https://github.com/apache/spark/pull/15708
[SPARK-18167] [SQL] Retry when the SQLQuerySuite test flakes
## What changes were proposed in this pull request?
This will re-run the flaky test a few times after it fails. This will help
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14547
**[Test build #67858 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67858/consoleFull)**
for PR 14547 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14547
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67858/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14547
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/15633
---
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/15693
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/15693
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67850/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15693
**[Test build #67850 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67850/consoleFull)**
for PR 15693 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15708
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67854/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15694
**[Test build #67856 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67856/consoleFull)**
for PR 15694 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15706
Actually is there a test case you can create for this? Make sure the test
case would fail when the patch is not applied.
---
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/15706
**[Test build #3385 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3385/consoleFull)**
for PR 15706 at commit
Github user wangmiao1981 commented on the issue:
https://github.com/apache/spark/pull/15697
@HyukjinKwon Thanks for your time!
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15709
(cc @nchammas too who I also guess met this issue first. I would like to
let him know.)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15666
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/15666
**[Test build #67860 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67860/consoleFull)**
for PR 15666 at commit
Github user mridulm commented on a diff in the pull request:
https://github.com/apache/spark/pull/13599#discussion_r85859191
--- Diff:
core/src/main/scala/org/apache/spark/api/python/PythonWorkerFactory.scala ---
@@ -55,6 +65,11 @@ private[spark] class
Github user mridulm commented on a diff in the pull request:
https://github.com/apache/spark/pull/13599#discussion_r85860115
--- Diff:
core/src/main/scala/org/apache/spark/api/python/PythonWorkerFactory.scala ---
@@ -69,6 +84,66 @@ private[spark] class
Github user mridulm commented on a diff in the pull request:
https://github.com/apache/spark/pull/13599#discussion_r85859768
--- Diff:
core/src/main/scala/org/apache/spark/api/python/PythonWorkerFactory.scala ---
@@ -69,6 +84,67 @@ private[spark] class
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15673
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67859/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15673
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
enabled
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15707
Looks like the test failed due to a flaky test, but other than that
everything else was fine. I'm going to merge this optimistically.
---
If your project is set up for it, you can reply to this
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15710
**[Test build #67874 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67874/consoleFull)**
for PR 15710 at commit
Github user zjffdu commented on a diff in the pull request:
https://github.com/apache/spark/pull/13599#discussion_r85877935
--- Diff:
core/src/main/scala/org/apache/spark/api/python/PythonWorkerFactory.scala ---
@@ -69,6 +84,66 @@ private[spark] class
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15710
cc @ericl, @marmbrus, @zsxwing and @lw-lin (I guess this would supersede
your old PR).
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/1
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 ericl commented on the issue:
https://github.com/apache/spark/pull/15708
Ok interesting, it seems the test repeatedly fails. This probably means it
is a suite ordering issue.
---
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 issue:
https://github.com/apache/spark/pull/15626
**[Test build #67829 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67829/consoleFull)**
for PR 15626 at commit
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/15699
cc @marmbrus
---
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
GitHub user zsxwing opened a pull request:
https://github.com/apache/spark/pull/15699
[SPARK-18030][Tests]Fix flaky FileStreamSourceSuite by not deleting the
files
## What changes were proposed in this pull request?
The test `when schema inference is turned on, should read
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/15695
Fixing the flaky test in #15699.
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15699
**[Test build #67830 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67830/consoleFull)**
for PR 15699 at commit
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/15670#discussion_r85826175
--- Diff: python/pyspark/serializers.py ---
@@ -64,7 +64,7 @@
from itertools import izip as zip
else:
import pickle
-protocol =
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15651
**[Test build #67802 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67802/consoleFull)**
for PR 15651 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15691
@rxin @cloud-fan @hvanhovell @tejasapatil @srowen @HyukjinKwon This PR is
now ready to review. This matrix can help us understand whether the implicit
casting has any bug. If any change is made
Github user andreweduffy commented on the issue:
https://github.com/apache/spark/pull/14649
Hey @paulata, sounds like you want to make the pruner pluggable at runtime.
That sounds like it would be good, though IMO is a bit orthogonal to this
change. This is more of an optimization
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15651
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/15651
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67802/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15651
**[Test build #67802 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67802/consoleFull)**
for PR 15651 at commit
Github user zjffdu commented on the issue:
https://github.com/apache/spark/pull/15669
@jerryshao spark.files is always passed to driver so SparkContext.addFile
is called in yarn-cluster.
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15692
**[Test build #67805 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67805/consoleFull)**
for PR 15692 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14640
OK let's close this one for now.
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/15672
**[Test build #67803 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67803/consoleFull)**
for PR 15672 at commit
Github user dreamworks007 commented on the issue:
https://github.com/apache/spark/pull/15616
@joshrosen - could you 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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15672
**[Test build #67803 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67803/consoleFull)**
for PR 15672 at commit
GitHub user zhengruifeng opened a pull request:
https://github.com/apache/spark/pull/15692
[SPARK-18177][ML][PYSPARK] Add missing 'subsamplingRate' of pyspark
GBTClassifier
## What changes were proposed in this pull request?
Add missing 'subsamplingRate' of pyspark
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15690
@rxin A good idea! Then, users can turn it off! Will submit a separate PR
for it. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/15663
---
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 liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/15651#discussion_r8567
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/ExistingRDD.scala ---
@@ -130,17 +130,40 @@ case class ExternalRDDScanExec[T](
/**
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/15651
LGTM except for one minor comment.
---
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/15691
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67801/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15691
**[Test build #67801 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67801/consoleFull)**
for PR 15691 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15691
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 viirya commented on the issue:
https://github.com/apache/spark/pull/15667
@snodawn Thanks! I will address dynamic partition in next commit.
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15672
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/15672
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67803/
Test PASSed.
---
Github user snodawn commented on the issue:
https://github.com/apache/spark/pull/15667
@viirya I have tested the newest patch. It performs good in running the
same sql as I ran before.
---
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 issue:
https://github.com/apache/spark/pull/15011
**[Test build #67804 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67804/consoleFull)**
for PR 15011 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15692
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/15692
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67805/
Test PASSed.
---
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15686
This change seems fine.
If Appveyor is encountering errors regularly, we might consider disabling
it, just because it wouldn't be giving useful information if most failures were
spurious.
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15603
Since this turned into a bit more of a change than where it started, and
because it removes a method (internal, defunct as it may be), and since this
isn't a hurry, would you open a JIRA just to
Github user kiszk commented on a diff in the pull request:
https://github.com/apache/spark/pull/15417#discussion_r85692528
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/optimizer/SimplifyCastsSuite.scala
---
@@ -44,7 +44,9 @@ class SimplifyCastsSuite extends
Github user jiangxb1987 commented on a diff in the pull request:
https://github.com/apache/spark/pull/15417#discussion_r85694427
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/optimizer/FilterPushdownSuite.scala
---
@@ -1016,6 +1016,8 @@ class
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/15669
From the code what I can is that `spark.files` will not be set in yarn mode.
```scala
OptionAssigner(args.files, LOCAL | STANDALONE | MESOS,
ALL_DEPLOY_MODES,
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15538
If this is necessary, then isn't it simpler to leave the log configuration
call where it was, so that it doesn't depend on the constructor? that wasn't
the actual problem was it, just the logging?
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/15651#discussion_r85690320
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/Dataset.scala ---
@@ -483,6 +484,60 @@ class Dataset[T] private[sql](
def isStreaming: Boolean =
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/15672
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 tdas commented on the issue:
https://github.com/apache/spark/pull/15663
Okay, I merged only to master, this does not merge cleanly to 2.0. I am on
vacation so i cant test out the 2.0 fix quickly, better make a separate PR for
2.0
---
If your project is set up for it,
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15637
**[Test build #67806 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67806/consoleFull)**
for PR 15637 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15692
**[Test build #67805 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67805/consoleFull)**
for PR 15692 at commit
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/15693
[SPARK-18125][SQL] Fix a compilation error in codegen due to splitExpression
## What changes were proposed in this pull request?
As reported in the jira, sometimes the generated java code
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15011
**[Test build #67804 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67804/consoleFull)**
for PR 15011 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15011
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67804/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15011
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/15693
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
301 - 400 of 572 matches
Mail list logo
