Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16404
MySQL treats them differently...
```SQL
mysql> select c1, concat(rand(), c1) from t1 group by c1;
+--+--+
| c1 | concat(rand(), c1) |
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16464
**[Test build #70863 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70863/testReport)**
for PR 16464 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/16460#discussion_r94537072
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/InsertIntoHadoopFsRelationCommand.scala
---
@@ -74,12 +69,29 @@ case class
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15880
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/15880
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70860/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16417
**[Test build #70862 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70862/testReport)**
for PR 16417 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15880
**[Test build #70860 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70860/testReport)**
for PR 15880 at commit
Github user ericl commented on a diff in the pull request:
https://github.com/apache/spark/pull/16460#discussion_r94536423
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/InsertIntoHadoopFsRelationCommand.scala
---
@@ -74,12 +69,29 @@ case class
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16404
Oracle allows it. It sounds like they treat ` (username ||
dbms_random.string('a', 10))` in aggregate and group-by as the same expression.
```SQL
SQL> select (username ||
Github user chengat1314 commented on the issue:
https://github.com/apache/spark/pull/14284
Is possible add feature to enable ignore nulls?
for example:
LAG (value_expr [, offset ])
[ IGNORE NULLS | RESPECT NULLS ]
OVER ( [ PARTITION BY window_partition ] ORDER BY
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/16460#discussion_r94535816
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/InsertIntoHadoopFsRelationCommand.scala
---
@@ -152,4 +190,29 @@ case class
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/16460#discussion_r94535760
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/DataSource.scala
---
@@ -473,22 +473,26 @@ case class DataSource(
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15178
**[Test build #70861 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70861/testReport)**
for PR 15178 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16469
---
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 viirya commented on the issue:
https://github.com/apache/spark/pull/15178
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 so,
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/15178
`org.apache.spark.rdd.AsyncRDDActionsSuite.async failure handling` passes
locally.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/16469
LGTM. Merging 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 feature
enabled and wishes
Github user merlintang commented on the issue:
https://github.com/apache/spark/pull/15819
@gatorsmile can you retest the patch, then we can merge. Sorry to ping you
multiple times since several users are asking this.
---
If your project is set up for it, you can reply to this email
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16308
@hvanhovell anything else to do here other than bringing it up to date?
---
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/16451
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/16451
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70858/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16451
**[Test build #70858 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70858/testReport)**
for PR 16451 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16469
some more explanation: when `Literal` codegen produce boxed values, the
double equality will break, because the code is `(Double.isNaN(d1) &&
Double.isNaN(d2)) || d == d2`
---
If your project
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16404
DB2 has such a limit. See the error message `SQL -583`:
http://www.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.messages.sql.doc/doc/msql00583n.html
> The routine
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/16460#discussion_r94533881
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/DataSource.scala
---
@@ -473,22 +473,26 @@ case class DataSource(
Github user zuotingbing commented on the issue:
https://github.com/apache/spark/pull/16439
@srowen i do not think there should be a fatal error since some of
SPARK_LOCAL_DIRS can be written successfully, even there is only one of
SPARK_LOCAL_DIRS can be written, the application is
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16461
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70856/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16461
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/16461
**[Test build #70856 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70856/testReport)**
for PR 16461 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16469
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/16469
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70855/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16469
**[Test build #70855 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70855/testReport)**
for PR 16469 at commit
Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/16469
Thanks for the quick fix!
---
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 a diff in the pull request:
https://github.com/apache/spark/pull/16460#discussion_r94532732
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/InsertIntoHadoopFsRelationCommand.scala
---
@@ -152,4 +190,29 @@ case class
Github user chengat1314 commented on the issue:
https://github.com/apache/spark/pull/14284
Are we able to enable ignore null feature in Spark 2.1?
like lag(comm ignore nulls) over (order by empno) prev_comm.
thx
---
If your project is set up for it, you can reply to this
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15178
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/15178
**[Test build #70857 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70857/testReport)**
for PR 15178 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15178
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70857/
Test FAILed.
---
Github user azmras commented on the issue:
https://github.com/apache/spark/pull/16429
just checked other things, ml, sql etc... everything is looking fine... I
can safely say goodbye to python 3.5 now...
Thank you.
---
If your project is set up for it, you can reply to
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/16455
whoa. 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 and wishes so, or
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16429
@azmras Thank you for confirming 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
Github user azmras commented on the issue:
https://github.com/apache/spark/pull/16429
Python 3.6.0 (default, Dec 24 2016, 08:01:42)
[GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.42.1)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/16417#discussion_r94529892
--- Diff:
sql/catalyst/src/main/java/org/apache/spark/sql/catalyst/expressions/UnsafeRow.java
---
@@ -201,6 +210,25 @@ public void setNullAt(int i) {
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/16417#discussion_r94529822
--- Diff:
sql/catalyst/src/main/java/org/apache/spark/sql/catalyst/expressions/UnsafeRow.java
---
@@ -201,6 +210,25 @@ public void setNullAt(int i) {
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16240
you need to fix mima:
```
[error] * method newDoubleSeqEncoder()org.apache.spark.sql.Encoder in
class org.apache.spark.sql.SQLImplicits does not have a correspondent in
current version
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16240
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/16240
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70859/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16240
**[Test build #70859 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70859/testReport)**
for PR 16240 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15880
**[Test build #70860 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70860/testReport)**
for PR 15880 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16240
**[Test build #70859 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70859/testReport)**
for PR 16240 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16240
LGTM, please create 2 more tickets for the optimization you metioned in
https://github.com/apache/spark/pull/16240#issuecomment-266318016 and the
nested custom collection.
---
If your project
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/15880
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 cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/16240#discussion_r94528665
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/DatasetPrimitiveSuite.scala ---
@@ -17,10 +17,21 @@
package org.apache.spark.sql
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16240
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 cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/16460#discussion_r94528412
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/InsertIntoHadoopFsRelationCommand.scala
---
@@ -74,12 +69,29 @@ case class
Github user cloud-fan closed the pull request at:
https://github.com/apache/spark/pull/16404
---
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 cloud-fan reopened a pull request:
https://github.com/apache/spark/pull/16404
[SPARK-18969][SQL] Support grouping by nondeterministic expressions
## What changes were proposed in this pull request?
Currently nondeterministic expressions are allowed in
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16404
How do other databases handle this case? Do they forbid using
non-deterministic expressions in GROUP BY, or give a better error message?
---
If your project is set up for it, you can reply to
Github user wzhfy commented on the issue:
https://github.com/apache/spark/pull/16422
@gatorsmile Why statistics info is sensitive? Users can run sql queries to
get each of them (max, min, ndv, etc) anyway.
---
If your project is set up for it, you can reply to this email and have
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16466
LGTM, if you can pass the test :)
---
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/16467
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70849/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16467
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/16451
**[Test build #70858 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70858/testReport)**
for PR 16451 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16467
**[Test build #70849 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70849/testReport)**
for PR 16467 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16451
Build started: [TESTS]
`org.apache.spark.streaming.kafka010.DirectKafkaStreamSuite`
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15178
**[Test build #70857 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70857/testReport)**
for PR 15178 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16453
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/16453
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70854/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16453
**[Test build #70854 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70854/testReport)**
for PR 16453 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/15178
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 so,
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16461
**[Test build #70856 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70856/testReport)**
for PR 16461 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15178
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70851/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15178
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/15178
**[Test build #70851 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70851/testReport)**
for PR 15178 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16469
**[Test build #70855 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70855/testReport)**
for PR 16469 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16402
Sorry it's my bad, I should take a look at the test result before retest
it. I've sent a PR to fix it.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16469
cc @kayousterhout @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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16465
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 cloud-fan opened a pull request:
https://github.com/apache/spark/pull/16469
[SPARK-19072][SQL] codegen of Literal should not output boxed value
## What changes were proposed in this pull request?
In https://github.com/apache/spark/pull/16402 we made a mistake
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16465
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70848/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16465
**[Test build #70848 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70848/testReport)**
for PR 16465 at commit
Github user mridulm commented on the issue:
https://github.com/apache/spark/pull/16462
LGTM, thanks for fixing this @kayousterhout !
---
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 yaooqinn commented on the issue:
https://github.com/apache/spark/pull/16445
ping @srowen would you plz take a look at 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 not have
Github user zhengruifeng commented on the issue:
https://github.com/apache/spark/pull/16457
Agreed. Now five algs inherit `HasWeightCol`: GLR/LoR/LiR/NB/IsotonicReg
I found that some algs use `RDD[Instance]` in `train` : GLR/LoR/LiR
```
val instances: RDD[Instance] =
Github user liujianhuiouc commented on the issue:
https://github.com/apache/spark/pull/16456
in actual scene, it's only one executor's director for an app, does you
mean that delete the child directories in parallel? in my opinion, it's
unnecessary to delete that in parallel, could
Github user zhengruifeng commented on the issue:
https://github.com/apache/spark/pull/16457
@srowen OK. This is the list of algs that deals with weights:
---
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/16453
**[Test build #70854 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70854/testReport)**
for PR 16453 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12775
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70844/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12775
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/12775
**[Test build #70844 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70844/testReport)**
for PR 12775 at commit
Github user zhengruifeng commented on the issue:
https://github.com/apache/spark/pull/16453
Updated. Thanks for reviewing.
---
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 kayousterhout commented on the issue:
https://github.com/apache/spark/pull/16402
This commit introduced a bug where IN doesn't work right for Infinity /
-Infinity (JIRA [here](https://issues.apache.org/jira/browse/SPARK-19072)).
I'm not sure how to fix the underlying bug
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16466
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/16466
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70847/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16466
**[Test build #70847 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70847/testReport)**
for PR 16466 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16468
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70853/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16468
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/16468
**[Test build #70853 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70853/testReport)**
for PR 16468 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16451
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/16451
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70843/
Test PASSed.
---
1 - 100 of 449 matches
Mail list logo
