[Buildbot-commits] [SPAM] Re: [Buildbot] #593: Flexible default logging.

[Buildbot]

#593: Flexible default logging.
-------------------+--------------------------------------------------------
Reporter:  verm    |       Owner:       
    Type:  defect  |      Status:  new  
Priority:  major   |   Milestone:  0.8.+
 Version:  0.7.11  |    Keywords:       
-------------------+--------------------------------------------------------
Description changed by dustin:

Old description:

> At the moment it's possible to specify logging (using default
> configurations) in only one way, which is to supply logfiles={}
>
> This has the disadvantage of streaming data in real time.  Not all logs
> during the build process require realtime streaming.
>
> Another issue is the stdio log, this copies both stdin and stderr to the
> same log file.
>
> It would be nice to have three specific features added to the default
> logging mech:
>
>  1. Specify different logfiles for stdin/stderr or other named pipes.
>  1. Specify a logfile that should only be uploaded at the _end_ of the
> build step, whether it fails or succeeds.  For example uploading
> config.status and config.log at the end running ./configure in a gnu
> autoconf setup.
>  1. The ability to specify a callback to filter a log file through.  For
> instance:
> {{{
> log(<input log on slave>, <callback function>, <log file to save on
> master>)
> }}}
> This would allow for filtering output from utilities that allow for
> custom log file output, such as `cl` from MSVC, or other utilities that
> may provided XML or other normalised output methods.

New description:

 At the moment it's possible to specify logging (using default
 configurations) in only one way, which is to supply logfiles={}

 This has the disadvantage of streaming data in real time.  Not all logs
 during the build process require realtime streaming.

 Another issue is the stdio log, this copies both stdin and stderr to the
 same log file.

 It would be nice to have three specific features added to the default
 logging mech:

  1. Specify different logfiles for stdin/stderr or other named pipes.
  1. Specify a logfile that should only be uploaded at the _end_ of the
 build step, whether it fails or succeeds.  For example uploading
 config.status and config.log at the end running ./configure in a gnu
 autoconf setup.
  1. The ability to specify a callback to filter a log file through.  For
 instance:
 {{{
 log(<input log on slave>, <callback function>, <log file to save on
 master>)
 }}}
 This would allow for filtering output from utilities that allow for custom
 log file output, such as `cl` from MSVC, or other utilities that may
 provided XML or other normalised output methods.

 Related:
  * #615

--

-- 
Ticket URL: <http://buildbot.net/trac/ticket/593#comment:3>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation