[ 
https://issues.apache.org/jira/browse/BEAM-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17128825#comment-17128825
 ] 

Beam JIRA Bot commented on BEAM-1890:
-------------------------------------

This issue is assigned but has not received an update in 30 days so it has been 
labeled "stale-assigned". If you are still working on the issue, please give an 
update and remove the label. If you are no longer working on the issue, please 
unassign so someone else may work on it. In 7 days the issue will be 
automatically unassigned.

> No INFO/DEBUG log if Python ValidatesRunner test timeout
> --------------------------------------------------------
>
>                 Key: BEAM-1890
>                 URL: https://issues.apache.org/jira/browse/BEAM-1890
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-py-core, testing
>            Reporter: Mark Liu
>            Assignee: Mark Liu
>            Priority: P3
>              Labels: beam-fixit, stale-assigned, triaged
>
> Python service test (ValidatesRunner test and Integration test with service 
> runner) enabled multiprocess execution in Postcommit through Nose. When 
> TimedOutException happens, only stack trace are printed out which contains 
> very little information about job info. Printing whatever logs until timeout 
> happens, which is captured by Nose, will make debugging on service more 
> easier.
> This is a issue on Nose framework side and there is a link to track: 
> https://github.com/nose-devs/nose/issues/1044



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to