Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/11751#issuecomment-197164762
LGTM assuming that MiMa checks pass.
---
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 JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/11748#discussion_r56284643
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskResultGetter.scala ---
@@ -81,8 +81,9 @@ private[spark] class TaskResultGetter(sparkEnv:
Github user breakdawn commented on the pull request:
https://github.com/apache/spark/pull/11735#issuecomment-197163774
Is it ok to test, or is there any action i can follow up?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11753#issuecomment-197163615
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11753#issuecomment-197163614
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11753#issuecomment-197163501
**[Test build #53275 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53275/consoleFull)**
for PR 11753 at commit
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/11748#discussion_r56284364
--- Diff:
core/src/test/scala/org/apache/spark/io/ChunkedByteBufferSuite.scala ---
@@ -0,0 +1,90 @@
+/*
+ * Licensed to the Apache Software
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/11748#discussion_r56284334
--- Diff:
core/src/main/scala/org/apache/spark/util/io/ChunkedByteBuffer.scala ---
@@ -0,0 +1,143 @@
+/*
+ * Licensed to the Apache Software
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/11751#issuecomment-197162819
@JoshRosen , I removed the legacy code and related comments now.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/11748#discussion_r56284289
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskResultGetter.scala ---
@@ -81,8 +81,9 @@ private[spark] class TaskResultGetter(sparkEnv: SparkEnv,
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/11748#discussion_r56284273
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskResultGetter.scala ---
@@ -81,8 +81,9 @@ private[spark] class TaskResultGetter(sparkEnv: SparkEnv,
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/11748#discussion_r56284277
--- Diff:
core/src/main/scala/org/apache/spark/util/io/ChunkedByteBuffer.scala ---
@@ -0,0 +1,143 @@
+/*
+ * Licensed to the Apache Software
Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/11721#discussion_r56284175
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -374,12 +374,6 @@ class SparkContext(config: SparkConf) extends Logging
with
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11751#issuecomment-197161777
**[Test build #53279 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53279/consoleFull)**
for PR 11751 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/11748#discussion_r56284073
--- Diff:
core/src/main/scala/org/apache/spark/util/io/ChunkedByteBuffer.scala ---
@@ -0,0 +1,143 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/11748#discussion_r56284010
--- Diff:
core/src/main/scala/org/apache/spark/util/io/ChunkedByteBuffer.scala ---
@@ -0,0 +1,143 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/11748#discussion_r56283999
--- Diff:
core/src/main/scala/org/apache/spark/util/io/ChunkedByteBuffer.scala ---
@@ -0,0 +1,143 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/11748#discussion_r56283991
--- Diff:
core/src/main/scala/org/apache/spark/util/io/ChunkedByteBuffer.scala ---
@@ -0,0 +1,143 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11730#issuecomment-197161220
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/11748#discussion_r56283895
--- Diff:
core/src/test/scala/org/apache/spark/io/ChunkedByteBufferSuite.scala ---
@@ -0,0 +1,90 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11730#issuecomment-197161216
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
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/11748#discussion_r56283941
--- Diff:
core/src/main/scala/org/apache/spark/util/io/ChunkedByteBuffer.scala ---
@@ -0,0 +1,143 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11730#issuecomment-197160978
**[Test build #53266 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53266/consoleFull)**
for PR 11730 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11694
---
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 pull request:
https://github.com/apache/spark/pull/11723#issuecomment-197159617
Hmm I'm not sure if it makes sense to create a public API for this at this
point. This is directly exposing something that is very internal to the current
implementation
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/11694#issuecomment-197159610
LGTM. Merged into master. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/11751#discussion_r56283381
--- Diff:
tools/src/main/scala/org/apache/spark/tools/GenerateMIMAIgnore.scala ---
@@ -39,12 +39,14 @@ import org.clapper.classutil.ClassFinder
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11645#issuecomment-197157889
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11645#issuecomment-197157899
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11742
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11645#issuecomment-197157762
**[Test build #53268 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53268/consoleFull)**
for PR 11645 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11742#issuecomment-197157622
**[Test build #53278 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53278/consoleFull)**
for PR 11742 at commit
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/11743#issuecomment-197157236
Will do that when implement codegen support.
---
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 JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/11751#discussion_r56282812
--- Diff:
tools/src/main/scala/org/apache/spark/tools/GenerateMIMAIgnore.scala ---
@@ -39,12 +39,14 @@ import org.clapper.classutil.ClassFinder
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/11721#issuecomment-197156547
I think `SchedulerExtensionService` can still be worked, since I still
maintain the full attempt id in `YarnScheduler`, only change to the simple
counter for Spark
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/10205#issuecomment-197156120
@vanzin I finally had some time to look over this change. I like the
direction this is going to apply more semantics for configs, but I find the
pre-existing SQLConf much
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11722#issuecomment-197155618
**[Test build #53277 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53277/consoleFull)**
for PR 11722 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11723#issuecomment-197154731
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11723#issuecomment-197154732
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11723#issuecomment-197154650
**[Test build #53264 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53264/consoleFull)**
for PR 11723 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11720#issuecomment-197154174
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11720#issuecomment-197154175
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11720#issuecomment-197154079
**[Test build #53265 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53265/consoleFull)**
for PR 11720 at commit
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/11692#issuecomment-197154066
I see your point, so the real issue should only be the log issue.
But marking the state as `FINISHED` with `SUCCEED` should be open to
question, since here
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11754#issuecomment-197153176
**[Test build #53274 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53274/consoleFull)**
for PR 11754 at commit
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/11713#issuecomment-197153189
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11722#issuecomment-197153188
**[Test build #53276 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53276/consoleFull)**
for PR 11722 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11753#issuecomment-197153177
**[Test build #53275 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53275/consoleFull)**
for PR 11753 at commit
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/11754#issuecomment-197152664
cc @hvanhovell
---
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 HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/11752#issuecomment-197152647
cc @yhuai
(Since the JIRA is pretty old one, I was confused if I should make a
follow-up like this but I just made this since it is a follow-up for the
GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/11754
[SPARK-13924][SQL] officially support multi-insert
## What changes were proposed in this pull request?
There is a feature of hive SQL called multi-insert. For example:
```
FROM
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/11752#issuecomment-197152653
Just to make sure, I am doing this partly due to
[SPARK-13764](https://issues.apache.org/jira/browse/SPARK-13764), which deals
with parse modes just like in CSV
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11694#issuecomment-197152626
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11694#issuecomment-197152624
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11694#issuecomment-197152557
**[Test build #53269 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53269/consoleFull)**
for PR 11694 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11713#issuecomment-197152507
cc @andrewor14
---
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 pull request:
https://github.com/apache/spark/pull/11752#issuecomment-197152532
Just to make sure, I am doing this partly due to
[SPARK-13764](https://issues.apache.org/jira/browse/SPARK-13764), which deals
with parse modes just like in CSV
GitHub user mwws opened a pull request:
https://github.com/apache/spark/pull/11753
[SPARK-13316][Streaming]add check to avoid registering new DStream when
recovering from CP
When creating a recoverable streaming job, it must be no new DStream
registered after a StreamingContext
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/11752#issuecomment-197152181
cc @yhuai
(Since the JIRA is pretty old one, I was confused if I should make a
follow-up like this but I just made this since it is a follow-up for the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11752#issuecomment-197152249
**[Test build #53273 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53273/consoleFull)**
for PR 11752 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11718
---
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 HyukjinKwon opened a pull request:
https://github.com/apache/spark/pull/11752
[SPARK-3308][SQL][FOLLOW-UP] Parse JSON rows having an array type and a
struct type in the same fieild
## What changes were proposed in this pull request?
This
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11718#issuecomment-197151890
Thanks - 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11718#issuecomment-197151328
**[Test build #2643 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2643/consoleFull)**
for PR 11718 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11737#issuecomment-197151199
**[Test build #53272 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53272/consoleFull)**
for PR 11737 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11722#issuecomment-197149789
**[Test build #53271 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53271/consoleFull)**
for PR 11722 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11751#issuecomment-197149790
**[Test build #53270 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53270/consoleFull)**
for PR 11751 at commit
GitHub user dongjoon-hyun opened a pull request:
https://github.com/apache/spark/pull/11751
[SPARK-13920][BUILD] MIMA checks should apply to @Experimental and
@DeveloperAPI APIs
## What changes were proposed in this pull request?
We are able to change `@Experimental` and
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11632#issuecomment-197144342
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11632#issuecomment-197144341
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11632#issuecomment-197144257
**[Test build #53261 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53261/consoleFull)**
for PR 11632 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11694#issuecomment-197143000
**[Test build #53269 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53269/consoleFull)**
for PR 11694 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11570#issuecomment-197142803
@vanzin I don't think anybody gets a ping message unless you explicitly cc
them. Will take a look.
---
If your project is set up for it, you can reply to this email and
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11553#issuecomment-197140007
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11553#issuecomment-197140010
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11553#issuecomment-197139782
**[Test build #53267 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53267/consoleFull)**
for PR 11553 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11645#issuecomment-197138848
**[Test build #53268 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53268/consoleFull)**
for PR 11645 at commit
Github user nongli commented on the pull request:
https://github.com/apache/spark/pull/11749#issuecomment-197135193
Can you add some test cases to columnarbatchsuite that exercises this?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user WangTaoTheTonic commented on the pull request:
https://github.com/apache/spark/pull/11692#issuecomment-197135484
the application is finished successfully(RM UI also show success state) but
log shows it failed, that's the problem i think.
yeah you're right sleep
Github user nongli commented on a diff in the pull request:
https://github.com/apache/spark/pull/11749#discussion_r56277661
--- Diff:
sql/core/src/main/java/org/apache/spark/sql/execution/vectorized/ColumnarBatch.java
---
@@ -58,6 +58,9 @@
// True if the row is filtered.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11709#issuecomment-197134877
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11709#issuecomment-197134881
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11709#issuecomment-197134624
**[Test build #53262 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53262/consoleFull)**
for PR 11709 at commit
Github user nongli commented on a diff in the pull request:
https://github.com/apache/spark/pull/11749#discussion_r56277607
--- Diff:
sql/core/src/main/java/org/apache/spark/sql/execution/vectorized/ColumnarBatch.java
---
@@ -284,11 +287,23 @@ public void reset() {
}
Github user nongli commented on a diff in the pull request:
https://github.com/apache/spark/pull/11749#discussion_r56277494
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/datasources/parquet/ParquetReadBenchmark.scala
---
@@ -299,10 +299,112 @@ object
Github user nongli commented on the pull request:
https://github.com/apache/spark/pull/11742#issuecomment-197133107
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
Github user nongli commented on a diff in the pull request:
https://github.com/apache/spark/pull/11742#discussion_r56277373
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/joins/BroadcastHashJoin.scala
---
@@ -322,4 +327,70 @@ case class BroadcastHashJoin(
Github user nongli commented on a diff in the pull request:
https://github.com/apache/spark/pull/11742#discussion_r56277324
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/joins/BroadcastHashJoin.scala
---
@@ -322,4 +327,70 @@ case class BroadcastHashJoin(
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11750#issuecomment-197131127
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11750#issuecomment-197131125
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11750#issuecomment-197131108
**[Test build #53263 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53263/consoleFull)**
for PR 11750 at commit
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/11713#issuecomment-197131091
cc @rxin @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
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/11750#discussion_r56276611
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/catalog/SessionCatalog.scala
---
@@ -0,0 +1,484 @@
+/*
+ * Licensed to the Apache
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/11692#issuecomment-197129360
But from my understanding, this exception does no harm to your application,
since your application is about to finish itself, also this may happen
occasionally.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11730#issuecomment-197128907
**[Test build #53266 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53266/consoleFull)**
for PR 11730 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11553#issuecomment-197128917
**[Test build #53267 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53267/consoleFull)**
for PR 11553 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11645#issuecomment-197128812
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11718#issuecomment-197128775
**[Test build #2643 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2643/consoleFull)**
for PR 11718 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11645#issuecomment-197128814
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11645#issuecomment-197128647
**[Test build #53258 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53258/consoleFull)**
for PR 11645 at commit
1 - 100 of 875 matches
Mail list logo
