On Thu, 6 Mar 2008, Eric Kow wrote: >> > And yes, I imagine it is a problem with the buildbot infrastructure, but >> > have little idea how to debug this. All I can think is to push a patch >> > changing the tests to be very verbose by default, and see where it is >> > hanging. Or perhaps you could run the buildbot daemon under strace (if >> > that exists on the mac?), and we could track what's going on that way. > > Is there a simple way to simulate locally the buildbot running?
I think so. Here are the commands we are asking buildbot to run: f1.addStep(step.Darcs, timeout=3600, repourl='http://darcs.net/repos/unstable', mode="copy") f1.addStep(step.Configure, command=['bash','-c','autoconf']) f1.addStep(step.Configure, command=['bash','-c','./configure']) f1.addStep(step.Compile, command=['bash','-c','make']) f1.addStep(step.Test, timeout=3600, command=['bash','-c','make test']) f1.addStep(step.Test, timeout=3600, command=['bash','-c','make test_network']) f1.addStep(step.Configure, command=['bash','./configure','--with-type-witnesses']) f1.addStep(step.Compile, command=['bash','-c','make clean']) f1.addStep(step.Compile, command=['bash','-c','make witnesses']) ### So, I think you can decode the shell commands it runs from that. Mark -- http://mark.stosberg.com/ _______________________________________________ darcs-devel mailing list darcs-devel@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-devel
