Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11033#issuecomment-220023317
**[Test build #58775 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58775/consoleFull)**
for PR 11033 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/12978#issuecomment-220021986
OK maybe, though here you show it took 0.5s.
---
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 WeichenXu123 commented on the pull request:
https://github.com/apache/spark/pull/12978#issuecomment-220021066
In order to check this potential problem more carefully, We can add the
following test code like this:
`
echo "$newpid" > "$pid"
**for i in
Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/13163#discussion_r63698118
--- Diff: launcher/src/main/java/org/apache/spark/launcher/Main.java ---
@@ -101,6 +110,80 @@ public static void main(String[] argsArray) throws
Exception
Github user kiszk commented on the pull request:
https://github.com/apache/spark/pull/11956#issuecomment-220019065
ping @davies
---
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 pull request:
https://github.com/apache/spark/pull/13129#issuecomment-220018776
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/13129#issuecomment-220018777
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/13129#issuecomment-220018623
**[Test build #58777 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58777/consoleFull)**
for PR 13129 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/12978#discussion_r63696847
--- Diff: sbin/spark-daemon.sh ---
@@ -162,6 +162,15 @@ run_command() {
esac
echo "$newpid" > "$pid"
+
+ for i in {1..10}
+
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12762#issuecomment-220017377
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/12762#issuecomment-220017229
**[Test build #58776 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58776/consoleFull)**
for PR 12762 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12762#issuecomment-220017380
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user WeichenXu123 commented on the pull request:
https://github.com/apache/spark/pull/12978#issuecomment-220016724
@srowen According to your suggestion, I add a loop to check whether it pass
STAGE-1 and launch java daemon. And I recover the check statement `! $(ps -p
"$newpid"
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13057#issuecomment-220013048
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/13057#issuecomment-220012940
**[Test build #58778 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58778/consoleFull)**
for PR 13057 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13057#issuecomment-220013044
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/13057#issuecomment-220009836
**[Test build #58778 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58778/consoleFull)**
for PR 13057 at commit
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/13135#issuecomment-220009767
I see. Thanks! I will change them tomorrow.
---
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/13129#issuecomment-220009820
**[Test build #58777 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58777/consoleFull)**
for PR 13129 at commit
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/13129#discussion_r63692508
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/regression/GeneralizedLinearRegression.scala
---
@@ -107,7 +107,7 @@ private[regression] trait
Github user MLnick commented on the pull request:
https://github.com/apache/spark/pull/13129#issuecomment-220009142
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12762#issuecomment-220008852
**[Test build #58776 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58776/consoleFull)**
for PR 12762 at commit
Github user MLnick commented on the pull request:
https://github.com/apache/spark/pull/12762#issuecomment-220008113
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13168#issuecomment-220007683
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/13168#issuecomment-220007682
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/13168#issuecomment-220007488
**[Test build #58769 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58769/consoleFull)**
for PR 13168 at commit
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/13139#discussion_r63690666
--- Diff: docs/ml-classification-regression.md ---
@@ -374,6 +374,197 @@ regression model and extracting model summary
statistics.
Github user yanboliang commented on the pull request:
https://github.com/apache/spark/pull/13139#issuecomment-220005824
@sethah I think we should also document the similarities and differences
between Spark GLM and R glm/glmnet.
---
If your project is set up for it, you can reply to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13170#issuecomment-220005341
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/13170#issuecomment-220005343
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/13139#discussion_r63689827
--- Diff: docs/ml-classification-regression.md ---
@@ -374,6 +374,197 @@ regression model and extracting model summary
statistics.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13167#issuecomment-220005056
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/13170#issuecomment-220005100
**[Test build #58772 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58772/consoleFull)**
for PR 13170 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13167#issuecomment-220005053
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 yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/13139#discussion_r63689657
--- Diff: docs/ml-classification-regression.md ---
@@ -374,6 +374,197 @@ regression model and extracting model summary
statistics.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13167#issuecomment-220004819
**[Test build #58773 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58773/consoleFull)**
for PR 13167 at commit
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/13139#discussion_r63689022
--- Diff: docs/ml-classification-regression.md ---
@@ -374,6 +374,197 @@ regression model and extracting model summary
statistics.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13170#issuecomment-220003377
**[Test build #2991 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2991/consoleFull)**
for PR 13170 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13008#issuecomment-220002209
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/13008#issuecomment-220002208
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 yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/13139#discussion_r63688136
--- Diff: docs/ml-classification-regression.md ---
@@ -374,6 +374,197 @@ regression model and extracting model summary
statistics.
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/13139#discussion_r63688193
--- Diff: docs/ml-classification-regression.md ---
@@ -374,6 +374,197 @@ regression model and extracting model summary
statistics.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13008#issuecomment-220001928
**[Test build #58771 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58771/consoleFull)**
for PR 13008 at commit
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/13120#discussion_r63687429
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/createDataSourceTables.scala
---
@@ -348,13 +349,23 @@ object
Github user MLnick commented on a diff in the pull request:
https://github.com/apache/spark/pull/13129#discussion_r63687411
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/regression/GeneralizedLinearRegression.scala
---
@@ -107,7 +107,7 @@ private[regression] trait
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13158#issuecomment-22704
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/13158#issuecomment-22568
**[Test build #58767 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58767/consoleFull)**
for PR 13158 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13158#issuecomment-22705
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user yanboliang commented on the pull request:
https://github.com/apache/spark/pull/13135#issuecomment-22072
One minor issue: Since we changed ```thresholds`` at Python example to
```[0.5, 0.5]```, should we also update Scala/Java examples to make them
consistent. Although
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/13120#discussion_r63686818
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/createDataSourceTables.scala
---
@@ -348,13 +349,23 @@ object
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/13120#discussion_r63686590
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/createDataSourceTables.scala
---
@@ -348,13 +349,23 @@ object
Github user akohli commented on the pull request:
https://github.com/apache/spark/pull/13130#issuecomment-219998908
sure (i get that) but 1000 is an arbitrary number that may or may not
sufficient. why not 10? why not 1?
---
If your project is set up for it, you can reply to
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11033#issuecomment-219998704
**[Test build #58775 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58775/consoleFull)**
for PR 11033 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13171#issuecomment-219996930
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/13171#issuecomment-219996920
**[Test build #58774 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58774/consoleFull)**
for PR 13171 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13171#issuecomment-219996926
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/13057#discussion_r63684617
--- Diff:
yarn/src/main/scala/org/apache/spark/deploy/yarn/YarnSparkHadoopUtil.scala ---
@@ -415,14 +416,14 @@ object YarnSparkHadoopUtil {
* the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13171#issuecomment-219995791
**[Test build #58774 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58774/consoleFull)**
for PR 13171 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/13057#discussion_r63684566
--- Diff:
yarn/src/main/scala/org/apache/spark/deploy/yarn/ExecutorRunnable.scala ---
@@ -128,6 +128,11 @@ private[yarn] class ExecutorRunnable(
}
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13042
---
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 pull request:
https://github.com/apache/spark/pull/13042#issuecomment-219995467
merged to master. I'm not against merging to 2.0.0 but wasn't sure how much
of a perf problem this is in normal usage.
---
If your project is set up for it, you can
GitHub user kiszk opened a pull request:
https://github.com/apache/spark/pull/13171
[SPARK-15380][SQL][WIP] Generate code that stores a float/double value in
each column from ColumnarBatch when DataFrame.cache() is used
## What changes were proposed in this pull request?
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13133
---
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 jurriaan commented on the pull request:
https://github.com/apache/spark/pull/13104#issuecomment-219994565
Looks like Test build #58759 failed randomly, right? Looks like it's all
green then, including the fix for SPARK-14463 :)
---
If your project is set up for it, you
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/13133#issuecomment-219994427
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13166
---
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 the pull request:
https://github.com/apache/spark/pull/13166#issuecomment-219992565
Merging 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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13145
---
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 pull request:
https://github.com/apache/spark/pull/13145#issuecomment-219991635
Merged to 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
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/9759#discussion_r63682344
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/datasources/json/JsonParsingOptionsSuite.scala
---
@@ -93,23 +93,45 @@ class
Github user techaddict commented on the pull request:
https://github.com/apache/spark/pull/13168#issuecomment-219991565
@srowen I checked this is only instance of `.set("master"` in the whole code
---
If your project is set up for it, you can reply to this email and have your
reply
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/9759#discussion_r63682088
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/datasources/json/JsonParsingOptionsSuite.scala
---
@@ -93,23 +93,45 @@ class
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13112
---
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 pull request:
https://github.com/apache/spark/pull/13112#issuecomment-219991039
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13094
---
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 pull request:
https://github.com/apache/spark/pull/13168#issuecomment-219990700
Can you check for other instances of this in other tests?
---
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/13162#issuecomment-219990713
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/13162#issuecomment-219990714
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/13162#issuecomment-219990499
**[Test build #58766 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58766/consoleFull)**
for PR 13162 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13162#issuecomment-219989695
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/13162#issuecomment-219989697
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/13162#issuecomment-219989489
**[Test build #58765 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58765/consoleFull)**
for PR 13162 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13133#issuecomment-219988257
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/13133#issuecomment-219988255
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/13133#issuecomment-219988174
**[Test build #58768 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58768/consoleFull)**
for PR 13133 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13167#issuecomment-219988062
**[Test build #58773 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58773/consoleFull)**
for PR 13167 at commit
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/13094#issuecomment-219988054
LGTM. Thanks for fixing it! Merging 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
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/13167#issuecomment-219987203
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13170#issuecomment-219987072
**[Test build #58772 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58772/consoleFull)**
for PR 13170 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13170#issuecomment-219987019
**[Test build #2991 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2991/consoleFull)**
for PR 13170 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/9759#discussion_r63679602
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/datasources/json/JsonParsingOptionsSuite.scala
---
@@ -93,23 +93,45 @@ class
GitHub user lianhuiwang opened a pull request:
https://github.com/apache/spark/pull/13170
[SPARK-15335] [SQL] Implement TRUNCATE TABLE Command
## What changes were proposed in this pull request?
Like TRUNCATE TABLE Command in Hive, TRUNCATE TABLE is also supported by
Hive.
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/12719#issuecomment-219986401
I'm ok to keep the `resolved` checking, if we can figure out why the test
failed and there is no easy workaround. Can you dig into it to see what
happened? Basically
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/9759#discussion_r63679038
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/datasources/json/JsonParsingOptionsSuite.scala
---
@@ -93,23 +93,45 @@ class
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/9759#discussion_r63678774
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/datasources/json/JsonParsingOptionsSuite.scala
---
@@ -93,23 +93,45 @@ class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13169#issuecomment-219985016
Can one of the admins verify this patch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
GitHub user wangyang1992 opened a pull request:
https://github.com/apache/spark/pull/13169
[SPARK-15379][SQL] check special invalid date
## What changes were proposed in this pull request?
When invalid date string like "2015-02-29 00:00:00" are cast as date or
timestamp
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13166#issuecomment-219983879
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/13167#issuecomment-219983786
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/13166#issuecomment-219983882
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
601 - 700 of 862 matches
Mail list logo
