[Buildbot-devel] Following of startup log in 0.8.10

[Ladyofthe Maple]

Okay, I now write this to the log instead of a '.'2015-02-18 19:29:46-0800 [-] Display BB key text so log follow continues - Starting BuildMaster
That fixed it :-) 

     On Wednesday, February 18, 2015 7:14 PM, Ladyofthe Maple <dianemaple76 at yahoo.com> wrote:
   

 AH!!!This is the code that watches the log file.It isn't that you have to keep logging SOMETHING every 10 seconds.You have to log one of a list of key texts.
Personally, that seems like the wrong thing to do...  If you haven't see the ending of startup text you are looking for then you should keep displaying the tail of the log.
From:"https://github.com/buildbot/buildbot/blob/master/master/buildbot/scripts/logwatcher.py"

Code:        # certain lines indicate progress, so we "cancel" the timeout        # and it will get re-added when it fires        PROGRESS_TEXT = ['Starting BuildMaster', 'Loading configuration from',                         'added builder', 'adding scheduler', 'Loading builder', 'Starting factory']        for progressText in PROGRESS_TEXT:            if progressText in line:                self.timer = None                break  

     On Wednesday, February 18, 2015 4:46 PM, Ladyofthe Maple <dianemaple76 at yahoo.com> wrote:
   

 Just to note the total time:<start>2015-02-18 16:43:34-0800 [-] Log opened.2015-02-18 16:43:34-0800 [-] twistd 14.0.2 (/usr/bin/python 2.7.6) starting up.2015-02-18 16:43:34-0800 [-] reactor class: twisted.internet.selectreactor.SelectReactor.2015-02-18 16:43:34-0800 [-] Starting BuildMaster -- buildbot.version: 0.8.10
No more than a 3 second pause in log entries during this time
2015-02-18 16:43:51-0800 [-] .2015-02-18 16:43:51-0800 [-] .2015-02-18 16:43:52-0800 [-] .2015-02-18 16:43:52-0800 [-] .2015-02-18 16:43:53-0800 [-] .
The buildmaster took more than 10 seconds to start, so we were unable toconfirm that it started correctly. Please 'tail twistd.log' and look for aline that says 'BuildMaster is Running' to verify correct startup.

 

     On Wednesday, February 18, 2015 4:24 PM, Ladyofthe Maple <dianemaple76 at yahoo.com> wrote:
   

 Hello,
I just went though a bit of trouble to make sure there is always something being printed while my master starts up.  Even when a task is running that takes a while with no output.I added a thread and a queue to allow me to print output from a spawned process or print a '.' if there isn't any output for a moment.ALL of this in order to make the log follower happy and not stop following after 10 seconds.... Why did the log follower STILL stop ?Here is the end of my startup output.
2015-02-18 16:17:47-0800 [-] 2015-02-18 16:17:48-0800 [-] .2015-02-18 16:17:48-0800 [-] .2015-02-18 16:17:48-0800 [-] .2015-02-18 16:17:48-0800 [-] .2015-02-18 16:17:49-0800 [-] .2015-02-18 16:17:49-0800 [-] .2015-02-18 16:17:49-0800 [-] .2015-02-18 16:17:49-0800 [-] .2015-02-18 16:17:50-0800 [-] .2015-02-18 16:17:50-0800 [-] .2015-02-18 16:17:50-0800 [-] .2015-02-18 16:17:50-0800 [-] .2015-02-18 16:17:51-0800 [-] .2015-02-18 16:17:51-0800 [-] .2015-02-18 16:17:51-0800 [-] .2015-02-18 16:17:51-0800 [-] .2015-02-18 16:17:52-0800 [-] .2015-02-18 16:17:52-0800 [-] .2015-02-18 16:17:52-0800 [-] .2015-02-18 16:17:52-0800 [-] .2015-02-18 16:17:53-0800 [-] .2015-02-18 16:17:53-0800 [-] .2015-02-18 16:17:53-0800 [-] .
The buildmaster took more than 10 seconds to start, so we were unable toconfirm that it started correctly. Please 'tail twistd.log' and look for aline that says 'BuildMaster is Running' to verify correct startup.
If I look in the twistd.log file I see that the dots never stopped being printed.So, what's going on here ?I use "print" to generate the output and it shows up in the log just fine.
2015-02-18 16:17:52-0800 [-] .2015-02-18 16:17:52-0800 [-] .2015-02-18 16:17:52-0800 [-] .2015-02-18 16:17:53-0800 [-] .2015-02-18 16:17:53-0800 [-] .2015-02-18 16:17:53-0800 [-] .2015-02-18 16:17:53-0800 [-] .2015-02-18 16:17:54-0800 [-] .2015-02-18 16:17:54-0800 [-] .2015-02-18 16:17:54-0800 [-] .2015-02-18 16:17:54-0800 [-] .2015-02-18 16:17:55-0800 [-] .2015-02-18 16:17:55-0800 [-] .2015-02-18 16:17:55-0800 [-] .2015-02-18 16:17:55-0800 [-] .2015-02-18 16:17:56-0800 [-] .2015-02-18 16:17:56-0800 [-] .2015-02-18 16:17:56-0800 [-] .
Thanks.
Diane



    

    

   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20150219/533bfdac/attachment.html>