[Buildbot-devel] `make clean' is too slow on buildbot

[Weongyo Jeong]

On Fri, Apr 23, 2010 at 11:11:05AM -0700, Rodney Stanton wrote:
> Weongyo,
>     How much data does the running of make clean send to the terminal? 
> To then be captured by buildbot.  Long ago, terminal speed limits would 
> slow down actions.  I doubt that's the case but since everything else is 
> being eliminated, I brought it up.
> 

I got 77 lines using wc(1) when I ran `make clean' and most lines aren't
over 80 columns.

And as you mentioned I tested the buildbot again with sending stdout to
/dev/null as follows:

- make_clean.sh -------------------------------------------------------
$ cat make_clean.sh 
#!/bin/sh
make clean > /dev/null

- master.cfg ----------------------------------------------------------

#f1.addStep(Compile(command=["make", "clean"], usePTY=True))
f1.addStep(Compile(command=["./make_clean.sh"]))

The result was same.

- result --------------------------------------------------------------

2010-04-23 11:27:41-0700 [Broker,client] ShellCommand._startCommand
2010-04-23 11:27:41-0700 [Broker,client]  ./make_clean.sh
2010-04-23 11:27:41-0700 [Broker,client]   in dir /home/buildbot/slave/project/build (timeout 1200 secs)
2010-04-23 11:27:41-0700 [Broker,client]   watching logfiles {}
2010-04-23 11:27:41-0700 [Broker,client]   argv: ['./make_clean.sh']
2010-04-23 11:27:41-0700 [Broker,client]  environment: {'LC_CTYPE': 'en_US.UTF-8', 'LESSOPEN': '|/usr/bin/lesspipe.sh %s', 'SSH_CLIENT': '10.10.255.161 54074 22', 'CVS_RSH': 'ssh', 'LOGNAME': 'deploy', 'USER': 'deploy', 'INPUTRC': '/etc/inputrc', 'HOME': '/root', 'PATH': '/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/home/deploy/bin:/usr/local/bin', 'LANG': 'en_US.UTF-8', 'TERM': 'xterm', 'SHELL': '/bin/bash', 'SHLVL': '3', 'G_BROKEN_FILENAMES': '1', 'HISTSIZE': '1000', '_': '/usr/bin/buildbot', 'PROJECT_PREFIX': '/home/buildbot/apps', 'SSH_CONNECTION': '10.10.255.161 54074 10.10.251.20 22', 'SSH_TTY': '/dev/pts/13', 'HOSTNAME': 'eng-20.sjc', 'PWD': '/home/buildbot/slave/project/build', 'MAIL': '/var/spool/mail/deploy', 'LS_COLORS': 'no=00:fi=00:di=00;34:ln=00;36:pi=40;33:so=00;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:ex=00;32:*.cmd=00;32:*.exe=00;32:*.com=00;32:*.btm=00;32:*.bat=00;32:*.sh=00;32:*.csh=00;32:*.tar=00;31:*.tgz=00;31:*.arj=00;31:*.taz=00;31:*.lzh=00;31:*.zip=00;31:*.z=00;31:*.Z=00;31:*.gz=00;31:*.bz2=00;31:*.bz=00;31:*.tz=00;31:*.rpm=00;31:*.cpio=00;31:*.jpg=00;35:*.gif=00;35:*.bmp=00;35:*.xbm=00;35:*.xpm=00;35:*.png=00;35:*.tif=00;35:'}
2010-04-23 11:27:41-0700 [Broker,client]   closing stdin
2010-04-23 11:27:41-0700 [Broker,client]   using PTY: False

==> master/twistd.log <==
2010-04-23 11:28:15-0700 [Broker,0,127.0.0.1] <RemoteShellCommand '['./make_clean.sh']'> rc=0
2010-04-23 11:28:15-0700 [-] closing log <buildbot.status.builder.LogFile instance at 0x617c2d8>
2010-04-23 11:28:15-0700 [-] releaseLocks(<buildbot.steps.shell.Compile instance at 0x617f998>): []
2010-04-23 11:28:15-0700 [-]  step 'compile_3' complete: success
2010-04-23 11:28:15-0700 [-] acquireLocks(step <buildbot.steps.shell.Compile instance at 0x617fc68>, locks [])
2010-04-23 11:28:15-0700 [-] ShellCommand.startCommand(cmd=<RemoteShellCommand '['make']'>)
2010-04-23 11:28:15-0700 [-]   cmd.args = {'workdir': 'build', 'env': {'PROJECT_PREFIX': '/home/buildbot/apps'}, 'want_stderr': 1, 'logfiles': {}, 'logEnviron': True, 'timeout': 1200, 'want_stdout': 1, 'usePTY': 'slave-config', 'maxTime': None}
2010-04-23 11:28:15-0700 [-] <RemoteShellCommand '['make']'>: RemoteCommand.run [5]
2010-04-23 11:28:15-0700 [-] command '['make']' in dir 'build'
2010-04-23 11:28:15-0700 [-] LoggedRemoteCommand.start

==> slave/twistd.log <==
2010-04-23 11:28:15-0700 [-] command finished with signal None, exit code 0, elapsedTime: 33.822761
2010-04-23 11:28:15-0700 [-] SlaveBuilder.commandComplete <buildbot.slave.commands.SlaveShellCommand instance at 0x2b75d8a79a28>

Are there any features for buildbot to run in the debugging mode?

regards,
Weongyo Jeong