[SPARK-8567] [SQL] Debugging flaky HiveSparkSubmitSuite

[liancheng]

Using similar approach used in HiveThriftServer2Suite to print stdout/stderr of the spawned process instead of logging them to see what happens on Jenkins. (This test suite only fails on Jenkins and doesn't spill out any log...)

cc @yhuai

[AmplabJenkins]

Merged build triggered.

[AmplabJenkins]

Merged build started.

[liancheng]

@yhuai Somehow I can partly reproduce this issue locally: no log in unit-tests.log, but didn't observed the timeout. After resorting to println rather than logInfo, I found out that one test case is trying to download Hive dependencies via Ivy. Opening this PR to see whether we can figure out what happens on Jenkins.

[SparkQA]

Test build #35657 has started for PR 6978 at commit b031647.

[SparkQA]

Test build #35657 has finished for PR 6978 at commit b031647.

• This patch fails MiMa tests.
• This patch merges cleanly.
• This patch adds no public classes.

[AmplabJenkins]

Merged build finished. Test FAILed.

[liancheng]

retest this please

[AmplabJenkins]

Merged build triggered.

[AmplabJenkins]

Merged build started.

[SparkQA]

Test build #35661 has started for PR 6978 at commit b031647.

[SparkQA]

Test build #35661 has finished for PR 6978 at commit b031647.

• This patch passes all tests.
• This patch merges cleanly.
• This patch adds no public classes.

[AmplabJenkins]

Merged build finished. Test PASSed.

[yhuai]

I am merging it to master. So, we will see the logs from these tests and start to debug why they can be slow.