Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15720
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67916/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15720
**[Test build #67916 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67916/consoleFull)**
for PR 15720 at commit
Github user wangmiao1981 commented on the issue:
https://github.com/apache/spark/pull/15697
@HyukjinKwon It seems that windows test still fails with the same error
---
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 issue:
https://github.com/apache/spark/pull/15541
**[Test build #67924 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67924/consoleFull)**
for PR 15541 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15710
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/15710
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/15710
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67912/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15710
**[Test build #67912 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67912/consoleFull)**
for PR 15710 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15710
**[Test build #67913 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67913/consoleFull)**
for PR 15710 at commit
Github user ericl commented on the issue:
https://github.com/apache/spark/pull/15673
@mallman shall we go ahead and revert that in this PR? It didn't help with
debugging the flaky test much.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15647
**[Test build #67923 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67923/consoleFull)**
for PR 15647 at commit
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/15546
Ah, I see. It's feature freeze. Thank you for informing me.
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15567
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/15546
Not rc, but the branch cut.
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15567
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67907/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15697
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/15697
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67920/
Test PASSed.
---
Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/15647
Any more comments, or shall I merge this?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/15647
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 so,
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15697
**[Test build #67920 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67920/consoleFull)**
for PR 15697 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15567
**[Test build #67907 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67907/consoleFull)**
for PR 15567 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15705
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67911/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15705
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/15705
**[Test build #67911 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67911/consoleFull)**
for PR 15705 at commit
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/15546
Oh, 2.1-rc1 today? I see.
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15688
Could we add all the positive and negative cases in `ExternalCatalogSuite`,
like the other APIs. Then, we can easily know whether the behaviors of
`InMemoryCatalog` and `HiveExternalCatalog` are
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15546
@dongjoon-hyun we are going to cut the release branch today (or tomorrow)
so it would be good to get this in asap.
---
If your project is set up for it, you can reply to this email and have your
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/15688#discussion_r86023753
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/catalog/InMemoryCatalog.scala
---
@@ -471,11 +471,30 @@ class InMemoryCatalog(
Github user sethah commented on the issue:
https://github.com/apache/spark/pull/15721
This issue also brings up a more general point of how sample weights should
be tested. It seems there are some common rules that all algorithms that
incorporate sample weights are thought to follow
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15721
**[Test build #67922 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67922/consoleFull)**
for PR 15721 at commit
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/15546
Sorry for delay, @rxin . I'm still working on, and will update in a few
days.
---
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 sethah opened a pull request:
https://github.com/apache/spark/pull/15721
[SPARK-17772][ML][TEST] Add test functions for ML sample weights
## What changes were proposed in this pull request?
More and more ML algos are accepting sample weights, and they have been
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14906
**[Test build #3390 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3390/consoleFull)**
for PR 14906 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/14906
LGTM if tests pass again.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15546
@dongjoon-hyun any update on this?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/15567#discussion_r86019635
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/Expression.scala
---
@@ -264,23 +264,43 @@ trait NonSQLExpression extends
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/15567#discussion_r86018687
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/Expression.scala
---
@@ -264,23 +264,43 @@ trait NonSQLExpression extends
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15704
**[Test build #67921 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67921/consoleFull)**
for PR 15704 at commit
Github user srowen closed the pull request at:
https://github.com/apache/spark/pull/15719
---
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 wangmiao1981 commented on the issue:
https://github.com/apache/spark/pull/15697
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 rxin commented on the issue:
https://github.com/apache/spark/pull/15719
Can you close this?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so,
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15704
**[Test build #67919 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67919/consoleFull)**
for PR 15704 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15697
**[Test build #67920 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67920/consoleFull)**
for PR 15697 at commit
Github user dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/15704#discussion_r86015221
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/ddl.scala ---
@@ -418,27 +419,53 @@ case class
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15659
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/15659
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67915/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #67915 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67915/consoleFull)**
for PR 15659 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15718
**[Test build #67918 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67918/consoleFull)**
for PR 15718 at commit
Github user rgbkrk commented on the issue:
https://github.com/apache/spark/pull/15659
As someone who followed #8318 consistently for a very long time, I can't
imagine this is only about it being at the end of a release cycle.
This is a critical issue for Python users.
---
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15659
BTW it is at the end of a release cycle right now so people are probably
focusing more on bugs or looking at critical issues.
---
If your project is set up for it, you can reply to this email and
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/15354
---
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/15659
What's the risk of having this in 2.1 after the branch is cut today? I
guess not very big since this is mostly additive?
---
If your project is set up for it, you can reply to this email and have
Github user marmbrus commented on the issue:
https://github.com/apache/spark/pull/15354
Thanks, I'm going to merge this 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 srowen commented on the issue:
https://github.com/apache/spark/pull/15719
Yep, sorry for this right in the middle of RC time. The change itself
should be a perfectly fine bug fix.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15719
Merging in branch-2.0. I'm waiting for this to cut rc2.
---
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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/15688#discussion_r86007181
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/catalog/InMemoryCatalog.scala
---
@@ -471,11 +471,30 @@ class InMemoryCatalog(
Github user itg-abby commented on the issue:
https://github.com/apache/spark/pull/15496
Sorry, I forgot to ping anyone after the last update.
@holdenk how does this look? What next steps should we take to push this PR?
---
If your project is set up for it, you can reply to this
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/15720
---
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 a diff in the pull request:
https://github.com/apache/spark/pull/15688#discussion_r86007168
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/catalog/InMemoryCatalog.scala
---
@@ -471,11 +471,30 @@ class InMemoryCatalog(
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15698
**[Test build #67917 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67917/consoleFull)**
for PR 15698 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15720
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/15720
**[Test build #67916 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67916/consoleFull)**
for PR 15720 at commit
Github user andrewor14 commented on the issue:
https://github.com/apache/spark/pull/15698
LGTM retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
GitHub user ericl opened a pull request:
https://github.com/apache/spark/pull/15720
[SPARK-18167] Disable flaky SQLQuerySuite test
We now know it's a persistent environmental issue that is causing this test
to sometimes fail. One hypothesis is that some configuration is leaked from
Github user sureshthalamati commented on the issue:
https://github.com/apache/spark/pull/15662
@rxin @gatorsmile
---
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 cmirash commented on the issue:
https://github.com/apache/spark/pull/15594
@steveloughran @yhuai Will you be able to help review this PR?
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/15719
**[Test build #67914 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67914/consoleFull)**
for PR 15719 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #67915 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67915/consoleFull)**
for PR 15659 at commit
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
jenkins retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
GitHub user srowen opened a pull request:
https://github.com/apache/spark/pull/15719
[SPARK-18114][HOTFIX] Fix line-too-long style error from backport of
SPARK-18114
## What changes were proposed in this pull request?
Fix style error introduced in cherry-pick of
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15677
I finished the last pass. Thanks for your work!
---
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 marmbrus commented on the issue:
https://github.com/apache/spark/pull/15702
Not a dumb question! You can certainly use processing time if those are
the semantics you require. I do think there is a little bit of work we need to
do to ensure determinism for these
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15703
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67910/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15703
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 jkbradley commented on the issue:
https://github.com/apache/spark/pull/15671
I just made a subtask for the algs covered here. Can you please link this
PR to SPARK-18206 in the title instead of the umbrella task?
---
If your project is set up for it, you can reply to
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15703
**[Test build #67910 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67910/consoleFull)**
for PR 15703 at commit
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/15677#discussion_r86000653
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/stringExpressions.scala
---
@@ -1200,7 +1333,7 @@ case class
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15710
**[Test build #67913 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67913/consoleFull)**
for PR 15710 at commit
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/15677#discussion_r85998364
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/stringExpressions.scala
---
@@ -1055,8 +1161,12 @@ case class
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/15677#discussion_r85999566
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/stringExpressions.scala
---
@@ -1200,7 +1333,7 @@ case class
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15710
**[Test build #67912 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67912/consoleFull)**
for PR 15710 at commit
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/15677#discussion_r85999505
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/stringExpressions.scala
---
@@ -1200,7 +1333,7 @@ case class
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15643
Ugh, the line became just a bit too long. HOTFIXing it straight away ...
---
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 gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/15677#discussion_r85998607
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/stringExpressions.scala
---
@@ -1177,7 +1305,12 @@ case class
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15643
Gah, let me go see what happened there and fix it @rxin. It looked clean
enough to cherry pick but I must have missed something
---
If your project is set up for it, you can reply to this email and
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/15677#discussion_r85997612
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/stringExpressions.scala
---
@@ -407,9 +436,15 @@ case class
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15697
**[Test build #67909 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67909/consoleFull)**
for PR 15697 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15697
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/15697
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67909/
Test FAILed.
---
Github user srinathshankar commented on a diff in the pull request:
https://github.com/apache/spark/pull/15637#discussion_r85993076
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/aggregate/MapAggregate.scala
---
@@ -0,0 +1,332 @@
+/*
+ *
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/15677#discussion_r85996873
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/regexpExpressions.scala
---
@@ -121,7 +121,7 @@ case class Like(left:
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/15677#discussion_r85996783
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/regexpExpressions.scala
---
@@ -68,7 +68,7 @@ trait
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/15677#discussion_r85996472
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/predicates.scala
---
@@ -410,7 +410,7 @@ object Equality {
}
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/15677#discussion_r85995869
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/nullExpressions.scala
---
@@ -168,7 +200,12 @@ case class Nvl2(expr1:
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15643
@srowen this broke the build in branch-2.0.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user tejasapatil commented on the issue:
https://github.com/apache/spark/pull/15605
@hvanhovell @cloud-fan @gatorsmile @yhuai : Any opinions about the approach
described in my previous comment ?
---
If your project is set up for it, you can reply to this email and have your
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15718
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67906/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15718
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/15718
**[Test build #67906 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67906/consoleFull)**
for PR 15718 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15705
**[Test build #67911 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67911/consoleFull)**
for PR 15705 at commit
301 - 400 of 740 matches
Mail list logo
