Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16509
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 feature
enabled and wishes so, or
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16509
**[Test build #3533 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3533/testReport)**
for PR 16509 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16509
**[Test build #3533 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3533/testReport)**
for PR 16509 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16509
Yeah I wonder if it's easy to test this in SparkSubmitSuite? I haven't
really thought through whether this would be able to test this code path. A
test would be nice; it depends on how hard it is.
Github user hustfxj commented on the issue:
https://github.com/apache/spark/pull/16509
@srowen @jerryshao I could't understand what you mean before this. Sorry!
Now I have fix the description here
---
If your project is set up for it, you can reply to this email and have your
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16509
(Noting this is a continuation of
https://github.com/apache/spark/pull/16443 ; there's no description here either)
---
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/16509
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 project does not have this
