[darcs-devel] buildbot failure in darcs on ertai Linux-2.6.18 i686

[zooko]

On Oct 15, 2008, at 9:11 AM, Matthias Kilian wrote:

> Is it possible to let the buildbot start with a *clean* environment.
> Or could somebody name the minimum set environment variables needed
> for the tests? Then we could scrub the environment with env(1).

Sure.  I'm not familiar with how to use env(1) for this purpose, but  
you can either change the master.cfg:

http://buildbot.darcs.net/master.cfg

To run tests in a different way than this:

     f.addStep(Test, command=["sh", "-c", make + " test"],  
description=["testing"], descriptionDone=["tested"], timeout=None)

Or else change the GNUmakefile to do something different when "make  
test" is invoked.

If we're doing it by changing master.cfg, then we can either write a  
new Python class which is a subclass of Test, and call it something  
like "EmptyEnvironmentTest", or else we could just put some shell  
scripting into the command list, like:

     f.addStep(Test, command=["sh", "-c", "env", make, "test"],  
description=["testing"], descriptionDone=["tested"], timeout=None)

Looking through the buildbot docs and source code don't show exactly  
how to mess with the environment of a shell command.  I think it  
might be something like:

class EmptyEnvironmentTest(Test):
     def setupEnvironment(self, cmd):
         Test.setupEnvironment(self, cmd)
         cmd.args['env'].clear()

Regards,

Zooko
---
http://allmydata.org -- Tahoe, the Least-Authority Filesystem
http://allmydata.com -- back up all your files for $5/month