[jira] [Updated] (HIVE-18212) Make sure Yetus check always has a full log

2017-12-11 Thread Peter Vary (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-18212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Vary updated HIVE-18212:
--
   Resolution: Fixed
Fix Version/s: 3.0.0
   Status: Resolved  (was: Patch Available)

Pushed to master.
Thanks for your patch [~szita]!

> Make sure Yetus check always has a full log
> ---
>
> Key: HIVE-18212
> URL: https://issues.apache.org/jira/browse/HIVE-18212
> Project: Hive
>  Issue Type: Sub-task
>Reporter: Adam Szita
>Assignee: Adam Szita
> Fix For: 3.0.0
>
> Attachments: HIVE-18212.0.patch
>
>
> Some yetus log files are left incomplete, and in these same runs {{tee}} 
> subprocesses are left running and dangling on the ptest server.
> This is because of a bug in the yetus runner velocity template script where 
> we make a redirection of stdout:
> {code}
> ./dev-support/test-patch.sh ${patchFile} . 2>&1 | tee ${logFile}
> {code}
> If the yetus output is big enough (>62K) tee will stop writing the log file 
> and is left running even after {{test-patch.sh}} finished successfully. This 
> because we don't make anything consume the stdout and most probably some 
> buffers get full on Linux side.
> We should also make sure that yetus runs(since they are executed parallel to 
> ptest test phase) are not interfering with each other in case they run very 
> long and overlap.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (HIVE-18212) Make sure Yetus check always has a full log

2017-12-04 Thread Adam Szita (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-18212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Szita updated HIVE-18212:
--
Status: Patch Available  (was: In Progress)

> Make sure Yetus check always has a full log
> ---
>
> Key: HIVE-18212
> URL: https://issues.apache.org/jira/browse/HIVE-18212
> Project: Hive
>  Issue Type: Sub-task
>Reporter: Adam Szita
>Assignee: Adam Szita
> Attachments: HIVE-18212.0.patch
>
>
> Some yetus log files are left incomplete, and in these same runs {{tee}} 
> subprocesses are left running and dangling on the ptest server.
> This is because of a bug in the yetus runner velocity template script where 
> we make a redirection of stdout:
> {code}
> ./dev-support/test-patch.sh ${patchFile} . 2>&1 | tee ${logFile}
> {code}
> If the yetus output is big enough (>62K) tee will stop writing the log file 
> and is left running even after {{test-patch.sh}} finished successfully. This 
> because we don't make anything consume the stdout and most probably some 
> buffers get full on Linux side.
> We should also make sure that yetus runs(since they are executed parallel to 
> ptest test phase) are not interfering with each other in case they run very 
> long and overlap.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (HIVE-18212) Make sure Yetus check always has a full log

2017-12-04 Thread Adam Szita (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-18212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Szita updated HIVE-18212:
--
Attachment: HIVE-18212.0.patch

> Make sure Yetus check always has a full log
> ---
>
> Key: HIVE-18212
> URL: https://issues.apache.org/jira/browse/HIVE-18212
> Project: Hive
>  Issue Type: Sub-task
>Reporter: Adam Szita
>Assignee: Adam Szita
> Attachments: HIVE-18212.0.patch
>
>
> Some yetus log files are left incomplete, and in these same runs {{tee}} 
> subprocesses are left running and dangling on the ptest server.
> This is because of a bug in the yetus runner velocity template script where 
> we make a redirection of stdout:
> {code}
> ./dev-support/test-patch.sh ${patchFile} . 2>&1 | tee ${logFile}
> {code}
> If the yetus output is big enough (>62K) tee will stop writing the log file 
> and is left running even after {{test-patch.sh}} finished successfully. This 
> because we don't make anything consume the stdout and most probably some 
> buffers get full on Linux side.
> We should also make sure that yetus runs(since they are executed parallel to 
> ptest test phase) are not interfering with each other in case they run very 
> long and overlap.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (HIVE-18212) Make sure Yetus check always has a full log

2017-12-04 Thread Adam Szita (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-18212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Szita updated HIVE-18212:
--
Description: 
Some yetus log files are left incomplete, and in these same runs {{tee}} 
subprocesses are left running and dangling on the ptest server.
This is because of a bug in the yetus runner velocity template script where we 
make a redirection of stdout:
{code}
./dev-support/test-patch.sh ${patchFile} . 2>&1 | tee ${logFile}
{code}
If the yetus output is big enough (>62K) tee will stop writing the log file and 
is left running even after {{test-patch.sh}} finished successfully. This 
because we don't make anything consume the stdout and most probably some 
buffers get full on Linux side.

We should also make sure that yetus runs(since they are executed parallel to 
ptest test phase) are not interfering with each other in case they run very 
long and overlap.

> Make sure Yetus check always has a full log
> ---
>
> Key: HIVE-18212
> URL: https://issues.apache.org/jira/browse/HIVE-18212
> Project: Hive
>  Issue Type: Sub-task
>Reporter: Adam Szita
>Assignee: Adam Szita
>
> Some yetus log files are left incomplete, and in these same runs {{tee}} 
> subprocesses are left running and dangling on the ptest server.
> This is because of a bug in the yetus runner velocity template script where 
> we make a redirection of stdout:
> {code}
> ./dev-support/test-patch.sh ${patchFile} . 2>&1 | tee ${logFile}
> {code}
> If the yetus output is big enough (>62K) tee will stop writing the log file 
> and is left running even after {{test-patch.sh}} finished successfully. This 
> because we don't make anything consume the stdout and most probably some 
> buffers get full on Linux side.
> We should also make sure that yetus runs(since they are executed parallel to 
> ptest test phase) are not interfering with each other in case they run very 
> long and overlap.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)