Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17344
No idea. We need to monitor the mvn builds more closely. This flaky test
case also impacts the sbt build.
Let me merge this first. Then, we can continue to clean the others.
---
If
Github user windpiger commented on the issue:
https://github.com/apache/spark/pull/17344
LGTMï¼but why maven test has this problemï¼
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17344
This test case passed, but we still have multiple other test cases 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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17344
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/17344
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74807/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17344
**[Test build #74807 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74807/testReport)**
for PR 17344 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/17344
cc @windpiger
---
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,
