Github user scwf commented on the pull request:
https://github.com/apache/spark/pull/2675#issuecomment-58188701
Hi @liancheng, I think i get the root cause here. In TestHive.scala we
reset the log4j level
```
// HACK: Hive is too noisy by default.
org.apache.log4j.LogManager.getCurrentLoggers.foreach { log =>
log.asInstanceOf[org.apache.log4j.Logger].setLevel(org.apache.log4j.Level.WARN)
}
```
So here the level is WARN and the process will not loginfo
"ThriftBinaryCLIService listening on", that lead to time out exception and test
failed.
Maybe we should reset log4j level here to test this:)
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
