GitHub user zjffdu opened a pull request:
https://github.com/apache/spark/pull/13598
[SPARK-13587] [PYSPARK] Support virtualenv in pyspark
## What changes were proposed in this pull request?
Support virtualenv in pyspark as described in SPARK-13587
## How was this patch
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13578
---
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 srowen commented on the issue:
https://github.com/apache/spark/pull/13578
Merged 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 and wishes so,
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13562
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60287/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13562
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/13562
**[Test build #60287 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60287/consoleFull)**
for PR 13562 at commit
Github user steveloughran commented on the issue:
https://github.com/apache/spark/pull/7786
> But I'm just trying to point out that the current change doesn't really
make things better. Without killing the executor, you'll still be holding on to
resources, except now you wouldn't be
Github user lw-lin commented on a diff in the pull request:
https://github.com/apache/spark/pull/13597#discussion_r66596861
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/DataFrameWriter.scala ---
@@ -572,8 +573,13 @@ final class DataFrameWriter[T] private[sql](ds:
GitHub user lw-lin opened a pull request:
https://github.com/apache/spark/pull/13597
[SPARK-15871][SQL] Add `assertNotPartitioned` check in `DataFrameWriter`
## What changes were proposed in this pull request?
Sometimes it doesn't make sense to specify partitioning
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13597
**[Test build #60292 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60292/consoleFull)**
for PR 13597 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13596
**[Test build #60291 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60291/consoleFull)**
for PR 13596 at commit
GitHub user ueshin opened a pull request:
https://github.com/apache/spark/pull/13596
[SPARK-15870][SQL] DataFrame can't execute after uncacheTable.
## What changes were proposed in this pull request?
If a cached `DataFrame` executed more than once and then do `uncacheTable`
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13594
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/13594
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60282/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13594
**[Test build #60282 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60282/consoleFull)**
for PR 13594 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/11956
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 lw-lin commented on a diff in the pull request:
https://github.com/apache/spark/pull/13595#discussion_r66589007
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/streaming/test/DataFrameReaderWriterSuite.scala
---
@@ -371,66 +371,80 @@ class
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13595
**[Test build #60290 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60290/consoleFull)**
for PR 13595 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/11956
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60285/
Test PASSed.
---
Github user lw-lin commented on a diff in the pull request:
https://github.com/apache/spark/pull/13595#discussion_r66588898
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/DataFrameWriter.scala ---
@@ -433,8 +433,7 @@ final class DataFrameWriter[T] private[sql](ds:
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/11956
**[Test build #60285 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60285/consoleFull)**
for PR 11956 at commit
GitHub user lw-lin opened a pull request:
https://github.com/apache/spark/pull/13595
[MINOR][SQL] Standardize 'continuous queries' to 'streaming
Datasets/DataFrames'
## What changes were proposed in this pull request?
This patch does some replacing (since `streaming
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13252
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/13252
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60284/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13252
**[Test build #60284 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60284/consoleFull)**
for PR 13252 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13576
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60283/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13576
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/13576
**[Test build #60283 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60283/consoleFull)**
for PR 13576 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/60281/
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 #60281 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60281/consoleFull)**
for PR 12836 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13590
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60289/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13590
**[Test build #60289 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60289/consoleFull)**
for PR 13590 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13590
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/13590
**[Test build #60289 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60289/consoleFull)**
for PR 13590 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13562
**[Test build #60288 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60288/consoleFull)**
for PR 13562 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/13590
Jenkins test 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 srowen commented on the issue:
https://github.com/apache/spark/pull/13591
I know this is bikeshedding, but I very slightly prefer this change.
Casting is uglier than using the 'right' method. I do understand "empty" is
slightly less familiar.
---
If your project is set
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13562
**[Test build #60287 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60287/consoleFull)**
for PR 13562 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/13562
Jenkins test 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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/13594#discussion_r66583343
--- Diff: core/src/main/scala/org/apache/spark/util/AccumulatorV2.scala ---
@@ -415,15 +415,20 @@ class DoubleAccumulator extends
AccumulatorV2[jl.Double,
Github user a-roberts commented on the issue:
https://github.com/apache/spark/pull/13562
Can we get this merged for the docs at least?
@JoshRosen, perhaps we could add some logic for the build command in the
Jenkins job to determine how many threads to run with (how many are
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13560
---
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 srowen commented on the issue:
https://github.com/apache/spark/pull/13560
Merged 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 and wishes so,
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13413
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/13413
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60279/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13413
**[Test build #60279 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60279/consoleFull)**
for PR 13413 at commit
Github user robbinspg commented on the issue:
https://github.com/apache/spark/pull/13589
As Adam says I still get the segv with OpenJDK on linux amd64 running our
app. This fix does appear to fix the issue reported in
https://issues.apache.org/jira/browse/SPARK-15825
---
If your
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/12894
**[Test build #60286 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60286/consoleFull)**
for PR 12894 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12894
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/12894
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60286/
Test FAILed.
---
Github user a-roberts commented on the issue:
https://github.com/apache/spark/pull/13589
Still getting seg faults on Power and with Intel on OpenJDK with this
change when we use spark-submit with two worker instances.
Git diff
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/12894
**[Test build #60286 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60286/consoleFull)**
for PR 12894 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13593
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60278/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13593
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/13593
**[Test build #60278 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60278/consoleFull)**
for PR 13593 at commit
Github user markhamstra commented on the issue:
https://github.com/apache/spark/pull/13591
Yeah, I wouldn't bother. The way this PR does it is arguably better
because it can be done consistently across all collections:
```scala
val l0 = List.empty[String]
val s0 =
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/60276/
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 #60276 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60276/consoleFull)**
for PR 12836 at commit
Github user wangyang1992 commented on a diff in the pull request:
https://github.com/apache/spark/pull/13585#discussion_r66575743
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/planning/patterns.scala
---
@@ -92,6 +92,36 @@ object PhysicalOperation extends
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/11956
**[Test build #60285 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60285/consoleFull)**
for PR 11956 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13252
**[Test build #60284 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60284/consoleFull)**
for PR 13252 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13560
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60280/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13560
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/13560
**[Test build #60280 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60280/consoleFull)**
for PR 13560 at commit
GitHub user HyukjinKwon reopened a pull request:
https://github.com/apache/spark/pull/13252
[SPARK-15473][SQL] CSV data source fails to write and read back empty data
## What changes were proposed in this pull request?
This PR adds the support for writing and reading back
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13576
**[Test build #60283 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60283/consoleFull)**
for PR 13576 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13594
**[Test build #60282 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60282/consoleFull)**
for PR 13594 at commit
Github user HyukjinKwon closed the pull request at:
https://github.com/apache/spark/pull/13252
---
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
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/13594
cc @cloud-fan
---
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 rxin opened a pull request:
https://github.com/apache/spark/pull/13594
[SPARK-15866] Rename listAccumulator collectionAccumulator
## What changes were proposed in this pull request?
SparkContext.listAccumulator, by Spark's convention, makes it sound like
"list" is a
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13415
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60275/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13415
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 rxin commented on the issue:
https://github.com/apache/spark/pull/13591
I'm actually not sure this is better in readability in either, since most
people know about None/Some/Option, but not necessarily Option.empty (I didn't
know about this before your pr).
---
If your
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13415
**[Test build #60275 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60275/consoleFull)**
for PR 13415 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/13576
Sure!
---
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 techaddict commented on the issue:
https://github.com/apache/spark/pull/13591
No performance benefits but improves readability.
On Fri, Jun 10, 2016 at 12:49 PM, Reynold Xin
wrote:
> Is this actually an improvement? Might be
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13587
---
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/13587
Thanks - merging in master/2.0/1.6.
---
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/13591
Is this actually an improvement? Might be too trivial to bother doing.
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/12836
**[Test build #60281 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60281/consoleFull)**
for PR 12836 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13560
**[Test build #60280 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60280/consoleFull)**
for PR 13560 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/13576
Can you change overwrite to override? We are overriding settings, not
overwriting the values.
---
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/13342
---
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 tdas commented on the issue:
https://github.com/apache/spark/pull/13342
Merging this to master and 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
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/13576#discussion_r66569746
--- Diff: python/pyspark/sql/readwriter.py ---
@@ -327,6 +334,8 @@ def csv(self, path, schema=None, sep=None,
encoding=None, quote=None, escape=Non
Github user zhengruifeng commented on a diff in the pull request:
https://github.com/apache/spark/pull/13560#discussion_r66569553
--- Diff: python/pyspark/mllib/evaluation.py ---
@@ -183,7 +183,7 @@ class MulticlassMetrics(JavaModelWrapper):
0.66...
>>>
Github user clockfly commented on a diff in the pull request:
https://github.com/apache/spark/pull/13585#discussion_r66569556
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/planning/patterns.scala
---
@@ -92,6 +92,36 @@ object PhysicalOperation extends
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13342
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/13342
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60274/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13342
**[Test build #60274 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60274/consoleFull)**
for PR 13342 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13571
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/13571
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60273/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13571
**[Test build #60273 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60273/consoleFull)**
for PR 13571 at commit
Github user kiszk commented on a diff in the pull request:
https://github.com/apache/spark/pull/13589#discussion_r66568805
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/codegen/CodeGenerator.scala
---
@@ -490,6 +490,7 @@ class CodegenContext {
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/13589
cc @davies
mystery of INPUT_ROW...
---
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/13413
**[Test build #60279 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60279/consoleFull)**
for PR 13413 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13591
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/13591
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60272/
Test PASSed.
---
501 - 600 of 618 matches
Mail list logo