[Buildbot-devel] More Win32 trouble

[Eric Hanchrow]

(Sorry if this appears twice; my first attempt didn't seem to get through)

I've read many messages about trouble running slaves on Win32; I have
a few experiences of my own to add.

This is buildbot 0.6.2

Here's what I did, and what I saw.  Unless otherwise noted, all the
commands that I typed appeared to work OK.  I used "write" to edit the
files; whenever I saved them, and it whined about how saving them in
"text-only" format would omit any formatting, I just clicked the "Yes"
button.

* Installed Python 2.4 on a Windows 2000 machine (from the .msi
  file).  I accepted all the installer's defaults.

* Installed the "pywin32 extensions", build 203.  I accepted all the
  installer's defaults.  (I can't remember the details, but something
  doesn't work if the pywin32 extensions aren't installed).

* Installed Twisted 1.3.0 (Python 2.4).  I accepted all the
  installer's defaults.

* In order to work around http://twistedmatrix.com/bugs/issue747, I
  edited c:\python23\scripts\mktab.bat, by replacing ``%1 %2 %3 %4 %5
  %6 %7 %8 %9'' with ``%*''

* I unpacked buildbot-0.6.2.tar.gz into
  c:\cygwin\usr\local\src\buildbot-0.6.2 with Cygwin tar.

* In order to work around
  https://sourceforge.net/tracker/index.php?func=detail&aid=1109469&group_id=73177&atid=537001,
  I edited contrib\windows\buildbot.bat by replacing "Python23" with
  "Python24".

* I went to the "My Computer" icon, and added
  "c:\python24;c:\python24\scripts" to my PATH.

* I started a new cmd.exe, and "cd"d to the buildbot directory
  c:\cygwin\usr\local\src\buildbot-0.6.2.

* I typed ``python setup.py install''.

* I "cd"d to c:\

* I typed "buildbot master c:\bb".

* I edited the master.cfg file; I've attached it below.

* I typed "buildbot start c:\bb".  I ignored a stack trace that
  indicated a failure deleting c:\bb\full\builder (No such file or
  directory), since I didn't understand it.

* I pointed my web browser at localhost:8010, and saw a
  reasonable-looking web page that said that buildbot-full was
  offline.  (It might also have said that there was no slave; that's
  reasonable too, since I hadn't yet created one.)

* At another command prompt, I typed ``buildbot slave c:\bbs
  localhost:9989 bot1name bot1passwd".

* I "cd"d to c:\bbs, and typed "mkdir info", then "cd info", then "echo
  me > admin" and "echo yowza > host".

* I "cd"d to c:\, and typed "buildbot start c:\bbs".

* I went back to the web browser, clicked on "buildbot-full", and
  clicked the "Force Build" button.

* The web browser implied that it was still building, which made me
  suspicious, so I looked at the cmd.exe in which I'd started the
  slave; it showed a stack trace which ended with an error from
  CreateProcess: "The directory name is invalid".  Unfortunately, I
  couldn't see the name of the invalid directory anywhere in the stack
  trace.

* Back in the web browser, I clicked on the "Build 0" link; I then
  clicked the "Stop Builder" button.  That appeared to work, but I
  then clicked the "log" link and saw

        command 'dir c:\' in dir c:\bbs\full\build (timeout 1200 secs)

  I also noticed that the web browser (Firefox 1.0.1) was acting as if
  it were still receiving information from the web server: the cursor
  had an hourglass next to it, and the little spinning-dots-doohickey
  in the upper-right corner was spinning.  I checked the slave window,
  and saw

...

        msg += ", killing pid %d" % self.process.pid
    exceptions.AttributeError: ShellCommand instance has no attribute 'process'

At this point I gave up :-(

-------------- next part --------------
A non-text attachment was scrubbed...
Name: master.cfg
Type: application/octet-stream
Size: 721 bytes
Desc: master config
URL: <http://buildbot.net/pipermail/devel/attachments/20050228/5bebcd6f/attachment.obj>
-------------- next part --------------

-- 
Governing the U.S. is like playing 200 simultaneous chess
matches (while whiny columnists second-guess every move on every
board).
        -- Nicholas Kristof, New York Times columnist