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

Valentyn Tymofieiev edited comment on BEAM-6603 at 2/6/19 11:32 PM:
--------------------------------------------------------------------

We looked at this together with [~markflyhigh] - turns out, this excessive 
debug output in nose is triggered by a use of logging.warning() in setup.py: 
[https://github.com/apache/beam/blob/75eb411ee85a4cf3862d42ae3d6a705cc516709e/sdks/python/setup.py#L174]


was (Author: tvalentyn):
Turns out, this excessive debug output in nose is triggered by a use of 
logging.warning() in setup.py: 
https://github.com/apache/beam/blob/75eb411ee85a4cf3862d42ae3d6a705cc516709e/sdks/python/setup.py#L174

> Python Pre/PostCommit generate huge console log
> -----------------------------------------------
>
>                 Key: BEAM-6603
>                 URL: https://issues.apache.org/jira/browse/BEAM-6603
>             Project: Beam
>          Issue Type: Bug
>          Components: build-system, testing
>            Reporter: Mark Liu
>            Priority: Major
>          Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> From the history of beam_PreCommit_Python_Cron, Huge console log are 
> generated starting from [this 
> build|https://builds.apache.org/job/beam_PreCommit_Python_Cron/914/]. About 
> 30MB console log is generated and most of them are INFO and DEBUG log from 
> pipeline running. This causes [console 
> output|https://builds.apache.org/job/beam_PreCommit_Python_Cron/914/console] 
> load very slow and no gradle scan is available due to too large logs.
> Three commit changes since last build seems not related to logging 
> configuration. Not sure if it's related to other changes that's not listed 
> there or the Jenkins update.
> Currently we can disable nose flag 
> [`--nocapture`|https://github.com/apache/beam/search?q=nocapture&type=Code] 
> that's passed to integration tests, so that stdout will be captured by nose 
> and only print if test fails. However, we should understand why those logs 
> are enabled and control it properly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to