[
https://issues.apache.org/jira/browse/BEAM-6603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Liu updated BEAM-6603:
---------------------------
Description:
>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.
was:
>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` 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.
> 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
>
> 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)
