[GitHub] spark issue #16096: [SPARK-18617][BACKPORT] backport to branch-2.0
Github user rxin commented on the issue: https://github.com/apache/spark/pull/16096 Can you use a meaningful title & description instead of saying backport? This is important because it becomes part of the commit history. You can put the backport message in the body. 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 not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org
[GitHub] spark issue #16096: [SPARK-18617][BACKPORT] backport to branch-2.0
Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/16096 **[Test build #69455 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69455/consoleFull)** for PR 16096 at commit [`76e0143`](https://github.com/apache/spark/commit/76e01432398295f8c48606dbba4847eede3815a2). --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org
