{5} Assigned, Active Tickets by Owner (Full Description) (17 matches)

While it creates working buildbot.exe, and the buildbot_serivce.exe works too. It can't start and gives the following traceback:

BuildBot for directory u'c:\\buildbot' terminated with exit code 255.
Traceback (most recent call last):
  File "boot_service.py", line 200, in <module>
  File "buildbot_service.pyc", line 502, in HandleCommandLine
  File "buildbot_service.pyc", line 482, in _RunChild
  File "os.pyc", line 444, in __delitem__
KeyError: 'PYTHONPATH'

It looks like PYTHONPATH is not defined when running in py2exe env? (I don't know enough about py2exe to debug this currently)

If the slave directory has spaces in it, BB gets completely confused if following  http://trac.buildbot.net/wiki/RunningBuildbotOnWindows

It appears that the directory gets broken up on space boundaries, and if you explicitly add double-quotes to prevent that, the entire string (including quotes) is interpreted as a path _relative_ to buildbot's installation in site-packages/

That wiki page should include 2 prominent warnings about this pitfall until the actual problem is fixed.

At one point I was using doxygen for documentation. While I'm not longer using it I figured the build step could be useful for others. Attached is the buildstep.

Example:

<neunon> CrawlBuild?, force build crawl-debug-x86_64-centos attempt to bomb with rvollmert's latest changes <CrawlBuild?> Something bad happened (see logs): <type 'exceptions.ValueError?'>

Gives:

2009-10-22 00:45:22-0700 [IrcStatusBot?,client] irc command force 2009-10-22 00:45:22-0700 [IrcStatusBot?,client] Unhandled Error

Traceback (most recent call last):

File "/usr/lib/python2.6/site-packages/twisted/words/protocols/irc.py", line 1484, in lineReceived

self.handleCommand(command, prefix, params)

File "/usr/lib/python2.6/site-packages/twisted/words/protocols/irc.py", line 1496, in handleCommand

method(prefix, params)

File "/usr/lib/python2.6/site-packages/twisted/words/protocols/irc.py", line 1041, in irc_PRIVMSG

self.privmsg(user, channel, message)

File "/usr/lib/python2.6/site-packages/buildbot/status/words.py", line 724, in privmsg

contact.handleMessage(message, user)

--- <exception caught here> ---

File "/usr/lib/python2.6/site-packages/buildbot/status/words.py", line 635, in handleMessage

meth(args.strip(), who)

File "/usr/lib/python2.6/site-packages/buildbot/status/words.py", line 380, in command_FORCE

args = shlex.split(args) # TODO: this requires python2.3 or newer

File "/usr/lib/python2.6/shlex.py", line 279, in split

return list(lex)

File "/usr/lib/python2.6/shlex.py", line 269, in next

token = self.get_token()

File "/usr/lib/python2.6/shlex.py", line 96, in get_token

raw = self.read_token()

File "/usr/lib/python2.6/shlex.py", line 172, in read_token

raise ValueError?, "No closing quotation"

exceptions.ValueError?: No closing quotation

Should I be reporting this to Twisted or can you guys work around this?

And uh, it looks to me like this is a route to a security hole if it's not escaping the singlequote.

Currently Buildbot forgets the historical data it needs to compute ETA whenever it's restarted or (I think) reconfigured. According to Brian Warner in a buildbot-dev posting, this should not be too hard to fix:

The current scheme would require storing a dict of (metricname -> expectation) for each step. The builder pickle would be the most appropriate place for this.

Current ETA calculation scheme "If there are any metrics, use text-output based estimation, otherwise, fall back to time-based estimation" is not transparent at all. Some users might prefer the current "mix", while others would prefer to stick with time-only estimations, while even others probably would prefer what is described by Brian in http://buildbot.net/trac/ticket/540 etc.

Maybe It'd be a good idea to introduce some scheme for letting Buildbot users to choose which type of estimation method they prefer and Buildbot Developers to add new ways of calculating/estimating ETA easily.

How could this be done? The first though crossing my mind on how to implement this scheme is an optional setting in master.cfg, allowing user to choose default ETA calculation/estimation setting. And probably an optional step's parameter, allowing to override the default setting.

Brian Warner wrote:

On Sat, 24 Nov 2007 13:06:32 -0500 "Sergey A. Lipnevich" wrote:

In 0.7.6, adding log observer that produces new metrics is tricky because each new metric must be also mentioned in build step's progressMetrics member. Would it be better instead to declare all metrics provided by log observer in its class, and automatically add new metrics names to progressMetrics once the observer instance is added? I can file a ticket and submit a patch, I'm asking here first if it's a good idea to make this change.

I think that's a good idea. You'll need to double-check that the "expectations" are still filled in correctly.. it's been a long time since I looked at that code, but I seem to remember there is a place where we run through all steps and fill them with expectations from the previous build. We'd need to make sure that we enumerate the metrics before doing this setting-expectations phase.

The buildbot slave default timeout can be too short for us. Sometimes, 5sec isnt always enough, and we get following:

% cltbld$ buildbot start /Users/cltbld/macosx-slave1

Following twistd.log until startup finished.. The buildmaster took more than 5 seconds to start, so we were unable to confirm that it started correctly. Please 'tail twistd.log' and look for a line that says 'configuration update complete' to verify correct startup.

%

... even though slave started "normally", responds fine to pings from buildbot master, and does handle jobs just fine.

Some things would be made easier if we were to store build status in a database that could be read by other processes. SQLite would be a good starting point.