[Buildbot-devel] New issues with dependent schedulers not being run

[Kenneth Lareau]

Before anyone jumps on this; the problem got resolved.  Apparently
when some additional branches had been added there was a partial
failure to the setting up of the schedulers; unfortunately what I
did was correct the configuration and do a 'reconfig' instead of a
full restart.  My issues all stemmed from the apparent fact that a
reconfig will NOT touch schedulers if they seem correct, and in
this case the dependent and upstream schedulers were being left
untouched.  As soon as I did a clean shutdown and restart, all of
the builders and schedulers came up properly and the problem went
away.  I probably should have noticed this sooner, but a few debug-
ging statements (that initially weren't being seen which tipped me
off to the fact that the schedulers weren't being set back up) was
what helped me resolve this issue.

Sorry for the false alarm.

Ken Lareau


Kenneth Lareau wrote:
> As a follow-up to my earlier email, it seems that my benchmarking
> schedulers no longer will run.  Some of the changes I have put in
> to ensure that they're only dependent off of the mainline branches
> of our products seem to be the culprit, but I can't tell for sure.
> Here's the output from a manhole process:
> 
>  >>> import pprint
>  >>> pprint.pprint([vars(a) for a in master.allSchedulers() if 
> repr(a).find('benchmark') != -1])
> [{'builderNames': ['benchmark ans-dist benchmarking-0'],
>    'name': 'benchmark-ans-dist-rhel-4-x86-64-0',
>    'namedServices': {},
>    'parent': <buildbot.master.BuildMaster instance at 0xb721910c>,
>    'running': 1,
>    'services': [],
>    'successWatchers': [],
>    'upstream': <Scheduler 'nightly-ans-dist-head-rhel-4-x86-64-0' at 
> -1297069620>
> },
>   {'builderNames': ['benchmark cns-dist benchmarking-0'],
>    'name': 'benchmark-cns-dist-rhel-4-x86-64-0',
>    'namedServices': {},
>    'parent': <buildbot.master.BuildMaster instance at 0xb721910c>,
>    'running': 1,
>    'services': [],
>    'successWatchers': [],
>    'upstream': <Scheduler 'nightly-cns-dist-head-rhel-4-x86-64-0' at 
> -1297070868>
> },
>   {'builderNames': ['benchmark navitas-dist benchmarking-0'],
>    'name': 'benchmark-navitas-dist-rhel-4-x86-64-0',
>    'namedServices': {},
>    'parent': <buildbot.master.BuildMaster instance at 0xb721910c>,
>    'running': 1,
>    'services': [],
>    'successWatchers': [],
>    'upstream': <Scheduler 'nightly-navitas-dist-head-rhel-4-x86-64-0' at 
> -1297068
> 692>},
>   {'builderNames': ['benchmark vantio-dist benchmarking-0'],
>    'name': 'benchmark-vantio-dist-rhel-4-i386-0',
>    'namedServices': {},
>    'parent': <buildbot.master.BuildMaster instance at 0xb721910c>,
>    'running': 1,
>    'services': [],
>    'successWatchers': [],
>    'upstream': <Scheduler 'nightly-vantio-dist-head-rhel-4-i386-0' at 
> -1339166676
>  >}]
> 
> 
> Let's pick the first upstream scheduler in the list:
> 
>  >>> pprint.pprint([vars(a) for a in master.allSchedulers() if 
> repr(a).find('nightly-ans-dist-head-rhel-4-x86-64-0') != -1])
> [{'branch': None,
>    'builderNames': ['ans-dist head rhel-4-x86-64-0'],
>    'dayOfMonth': '*',
>    'dayOfWeek': '*',
>    'delayedRun': <twisted.internet.base.DelayedCall instance at 0xb4d64b2c>,
>    'hour': [0],
>    'minute': 43,
>    'month': '*',
>    'name': 'nightly-ans-dist-head-rhel-4-x86-64-0',
>    'namedServices': {},
>    'nextRunTime': 1193557380.0,
>    'parent': <buildbot.master.BuildMaster instance at 0xb721910c>,
>    'running': 1,
>    'services': [],
>    'successWatchers': []}]
> 
> 
> Looking at an earlier email where I had a similar problem, I noticed
> that this time around, 'successWatchers' is empty where it should
> have a '<bound method Dependent.upstreamBuilt of <Scheduler 'benchmark-
> rhel-4-x86-64-0' at -XXXXXXXXXXXX>>'.  When I print out the information
> getting passed to the Dependent class for initialization, all the in-
> formation seems to be correct and there, so why am I not seeing a
> successWatchers entry?  Any suggestions on how to debug this further?
> 
> Thanks for any assistance that folks can give...
> 
> 
> Ken Lareau
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel