[
https://issues.apache.org/jira/browse/BEAM-6603?focusedWorklogId=195420&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-195420
]
ASF GitHub Bot logged work on BEAM-6603:
----------------------------------------
Author: ASF GitHub Bot
Created on: 06/Feb/19 23:23
Start Date: 06/Feb/19 23:23
Worklog Time Spent: 10m
Work Description: tvalentyn commented on issue #7752: [BEAM-6603] Fix
Python logging in setup.py
URL: https://github.com/apache/beam/pull/7752#issuecomment-461228573
Please also change __init__.py. We should use warning there as well instead
of warning, since it's semantically more appropriate. Thank you.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 195420)
Time Spent: 2h 20m (was: 2h 10m)
> 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 20m
> 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)
