Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7058#issuecomment-116766793
I'm testing out a slightly silly hack to see if I can prevent the spurious
AmplabJenkins errors: at the bottom of our Jenkins "execute shell" command, I'm
adding an extra call to `build/sbt unsafe/test`, which will run a Java test
suite which only takes maybe 5 seconds to run. This will ensure that we always
run at least one JVM-based test, which will create a JUnit XML test report;
this should suppress the "could not find test reports" warning from the Jenkins
JUnit plugin. Let's see if it works...
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
