[
https://issues.apache.org/jira/browse/HIVE-21629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laszlo Bodor updated HIVE-21629:
--------------------------------
Description:
While running a qtest, or running multiple qtests with the same driver,
user/dev can only see top level message for a long time:
{code}
[INFO] Running org.apache.hadoop.hive.cli.TestCliDriver
{code}
It would be helpful to introduce a cli argument to enable some realtime
monitoring. The challenge basically is that the tests run in separate surefire
JVMs, which basically log into surefire report files, and everything which is
logged with System.out can be found in that file:
{code}
itests/qtest/target/surefire-reports/org.apache.hadoop.hive.cli.TestCliDriver-output.txt
{code}
so, I would expect the same or similar behavior as with tailing that file in a
separate terminal
> Monitor qtest progress realtime on console
> ------------------------------------------
>
> Key: HIVE-21629
> URL: https://issues.apache.org/jira/browse/HIVE-21629
> Project: Hive
> Issue Type: Bug
> Reporter: Laszlo Bodor
> Priority: Major
>
> While running a qtest, or running multiple qtests with the same driver,
> user/dev can only see top level message for a long time:
> {code}
> [INFO] Running org.apache.hadoop.hive.cli.TestCliDriver
> {code}
> It would be helpful to introduce a cli argument to enable some realtime
> monitoring. The challenge basically is that the tests run in separate
> surefire JVMs, which basically log into surefire report files, and everything
> which is logged with System.out can be found in that file:
> {code}
> itests/qtest/target/surefire-reports/org.apache.hadoop.hive.cli.TestCliDriver-output.txt
> {code}
> so, I would expect the same or similar behavior as with tailing that file in
> a separate terminal
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
