[Buildbot-devel] Buildbot and Perforce

Tony Walker tony.walker at crocodile-clips.com
Wed Jun 1 08:18:10 UTC 2005

Hi Brian,

Thanks for the info, I will chase this up. I have followed the link to
the log from the 'update failed' red box before, it gave me the
following info:

starting p4 sync
rm -rf /home/developer/Buildbot_Slave/full/build
 in dir /home/developer/Buildbot_Slave/full (timeout 1200 secs)
 argv: ['rm', '-rf', '/home/developer/Buildbot_Slave/full/build']
 environment: {'SSH_ASKPASS': '/usr/libexec/openssh/gnome-ssh-askpass',
if=00;35:', 'LESSOPEN': '|/usr/bin/lesspipe.sh %s', 'SSH_CLIENT':
' 44391 22', 'LOGNAME': 'developer', 'USER': 'developer',
'INPUTRC': '/etc/inputrc', 'PATH':
l/bin:/home/developer/bin', 'QTDIR': '/usr/local/qt', 'P4PORT':
'', 'LD_LIBRARY_PATH': ':/usr/local/qt/lib', '_':
'/usr/bin/buildbot', 'LANG': 'en_GB.UTF-8', 'P4CLIENT': 'devbuilder0',
'TERM': 'xterm', 'SHELL': '/bin/bash', 'SHLVL': '1', 'SSH_TTY':
'/dev/ttyp6', 'OLDPWD': '/home/developer/Buildbot_Slave/full',
'HOSTNAME': 'devbuilder0', 'G_BROKEN_FILENAMES': '1', 'HISTSIZE':
'1000', 'PWD': '/home/developer', 'P4USER': 'Tony', 'MAIL':
'/var/spool/mail/developer', 'SSH_CONNECTION': ' 44391 22', 'HOME': '/home/developer'}
program finished with exit code -1

It doesn't really tell me why p4 failed. I would have thought that if it
was executing 'p4 sync' then I would see some complaints in the log, but
I can't see anything. It's almost as if it doesn't know what 'p4sync'
is? Is this a typical 'buildbot' log output or do I have to switch on a
flag to get more info?

Thanks for the help, appreciate it.

> -----Original Message-----
> From: Brian Warner [mailto:warner-buildbot at lothar.com]
> Sent: 31 May 2005 20:03
> To: tony.walker at crocodile-clips.com
> Cc: buildbot-devel at lists.sourceforge.net
> Subject: Re: [Buildbot-devel] Buildbot and Perforce
> > I am really interested in using buildbot as our build system here
but I
> > am having trouble combing perforce with a build slave. Perofrce and
> > view and client are set up correctly for the buildslave, but when
> > attempting to run a build it fails.
> Based upon those log messages, the 'p4 sync' command failed. There
> be
> more information (i.e. the stdout/stderr from the p4 command
> why
> it failed) in the log for that build step, available from your
> buildmaster's
> web page. Once the build has failed, you should see a red "p4 sync"
> with
> a "log" link.. just follow that link for more details.
> Note that step.P4Sync is really rudimentary: doesn't know how to setup
> view spec or check out an initial tree. It only knows how to run 'p4
> in
> a specified directory. You have to make sure that running that command
> that directory will do what you want. The directory will depend upon
> you've configured the builder, and will be announced in the log for
> step.P4Sync command, but it will be of the form:
>  slave_basedir + builddir + "source"
> hope that helps,
>  -Brian

More information about the devel mailing list