Github user lw-lin commented on the issue:
https://github.com/apache/spark/pull/15482
Now that td has issued a commit
https://github.com/apache/spark/commit/05800b4b4e7873ebc445dfcd020b76d7539686e1
exactly like this, I'm closing this. Sure `flaky-test` is more proper than
`hot-fix`
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15482
I think he met this in
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66954/testReport/
which seems a possibly flaky test. It seems several latest tests gone fine
though.
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15482
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/15482
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66959/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15482
**[Test build #66959 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66959/consoleFull)**
for PR 15482 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15482
Is this actually failing builds? I don't see that consistently at
https://amplab.cs.berkeley.edu/jenkins/view/Spark%20QA%20Test%20(Dashboard)/
---
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/15482
**[Test build #66959 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66959/consoleFull)**
for PR 15482 at commit
