Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/6957#issuecomment-117292935
@yhuai As for why the log doesn't appear on Jenkins, my guess is that the
`spark-submit` process wasn't started properly because of, for example, some
class not found error. I'd suggest to enable `SPARK_PRINT_LAUNCH_COMMAND`, then
login into a Jenkins worker node and try exactly the same command line there.
Currently, a super long classpath (it fills two and a half screens of mine...)
appear on Jenkins for this test suite. This might be the reason why this error
only appear on Jenkins, since classpath can be environment sensitive.
---
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]
