Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16309
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/16309
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70598/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16309
**[Test build #70598 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70598/testReport)**
for PR 16309 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16309
**[Test build #70598 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70598/testReport)**
for PR 16309 at commit
Github user jaceklaskowski commented on the issue:
https://github.com/apache/spark/pull/16309
For reference: [scala-xml
releases](https://github.com/scala/scala-xml/releases)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16309
In order to finish this thought, let's either update scalatest to just
1.12.6 if that solves it, or do nothing. In the latter case, you could leave
the JIRA open as an 'update to scalatest 3' JIRA
