You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/06/03 17:14:00 UTC

[jira] [Commented] (BEAM-1890) No INFO/DEBUG log if Python ValidatesRunner test timeout

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

Kenneth Knowles commented on BEAM-1890:
---------------------------------------

This issue has been migrated to https://github.com/apache/beam/issues/18254

> 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
>            Priority: P3
>              Labels: beam-fixit, 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.20.7#820007)