Opened 7 years ago

Last modified 6 years ago

#2923 new task

"simple" builds fail because Buidlbot is not installed

Reported by: dustin Owned by:
Priority: major Milestone: sys - metabuildbot
Version: 0.8.9 Keywords: windows


On the win8 builder:

Traceback (most recent call last):
  File "C:\Users\Public\buildslave\os-win81\build\master\buildbot\test\integration\", line 39, in test_sample_config
    config.MasterConfig.loadConfig(self.basedir, filename)
  File "C:\Users\Public\buildslave\os-win81\build\master\buildbot\", line 185, in loadConfig
    raise errors
buildbot.config.ConfigErrors: error while parsing config file: Unknown component name: BuildSlave (traceback in logfile)

Traceback (most recent call last):
  File "C:\Users\Public\buildslave\os-win81\build\master\buildbot\", line 175, in loadConfig
    exec f in localDict
  File "C:\Users\Public\buildslave\os-win81\build\master\buildbot\scripts\sample.cfg", line 18, in <module>
    c['slaves'] = [buildslave.BuildSlave("example-slave", "pass")]
  File "C:\Users\Public\buildslave\os-win81\build\master\buildbot\plugins\", line 238, in __getattr__
    raise AttributeError(str(err))
exceptions.AttributeError: Unknown component name: BuildSlave


This builder doesn't use a virtualenv -- in the metabbotcfg, it's a "simple" builder that just assumes the Python prerequisites (Twisted, etc.) are installed and then runs trial.

I suspect the fix is to use a virtualenv, but I remember struggling mightily to make such a thing work several years ago, and finally giving up and falling back to "simple".

Change History (2)

comment:1 Changed 7 years ago by dustin

I can work on this at some point, but it should be possible for someone else to look at the metabbotcfg repo ( and figure out a way to make the VirtualenvSetup? step ( work on Windows.

comment:2 Changed 6 years ago by dustin

I've had a hard time testing this since the buildslave seems to come on and offline frequently.

Note: See TracTickets for help on using tickets.