[Buildbot-commits] [Buildbot] #1883: How to solve it "step 'svn' complete: failure"

Buildbot nobody at buildbot.net
Tue Mar 15 14:59:51 UTC 2011


#1883: How to solve it "step 'svn' complete: failure"
----------------------------+--------------------
Reporter:  sanlokenpatidar  |       Owner:
    Type:  support-request  |      Status:  new
Priority:  major            |   Milestone:  0.8.+
 Version:  0.8.3p1          |  Resolution:
Keywords:                   |
----------------------------+--------------------

Old description:

> 2011-03-09 06:48:00-0500 [Broker,0,10.1.4.31] ping finished: success
> 2011-03-09 06:48:00-0500 [Broker,0,10.1.4.31] <Build
> pro4_full>.startBuild
> 2011-03-09 06:48:00-0500 [Broker,0,10.1.4.31] acquireLocks(step <Build
> pro4_full>, locks [])
> 2011-03-09 06:48:00-0500 [Broker,0,10.1.4.31] acquireLocks(step
> <buildbot.steps.source.SVN instance at 0xa9383ac>, locks [])
> 2011-03-09 06:48:00-0500 [Broker,0,10.1.4.31]
> ShellCommand.startCommand(cmd=<RemoteCommand 'svn' at 177440364>)
> 2011-03-09 06:48:00-0500 [Broker,0,10.1.4.31]   cmd.args = {'workdir':
> 'build', 'patch': None, 'retry': (60, 2), 'mode': 'clobber', 'timeout':
> 1200, 'svnurl':
> 'https://svn.codespaces.com/cybex/symphony/Pro4Sandboxtrunk', 'revision':
> None}
> 2011-03-09 06:48:00-0500 [Broker,0,10.1.4.31] <RemoteCommand 'svn' at
> 177440364>: RemoteCommand.run [0]
> 2011-03-09 06:48:00-0500 [Broker,0,10.1.4.31] LoggedRemoteCommand.start
> 2011-03-09 06:48:54-0500 [-] SVNPoller polling
> 2011-03-09 06:50:23-0500 [-] svnPoller: _process_changes last 13
> mostRecent 13
> 2011-03-09 06:50:23-0500 [-] svnPoller: _process_changes 13 .. 13
> 2011-03-09 06:50:23-0500 [-] SVNPoller finished polling
> 2011-03-09 06:50:23-0500 [-] _finished : None
> 2011-03-09 06:51:04-0500 [Broker,0,10.1.4.31] <RemoteCommand 'svn' at
> 177440364> rc=1
> 2011-03-09 06:51:04-0500 [-] closing log <buildbot.status.builder.LogFile
> instance at 0xa93874c>
> 2011-03-09 06:51:04-0500 [-] releaseLocks(<buildbot.steps.source.SVN
> instance at 0xa9383ac>): []
> 2011-03-09 06:51:04-0500 [-]  step 'svn' complete: failure
> 2011-03-09 06:51:04-0500 [-]  <Build pro4_full>: build finished

New description:

 {{{
 2011-03-09 06:48:00-0500 [Broker,0,10.1.4.31] ping finished: success
 2011-03-09 06:48:00-0500 [Broker,0,10.1.4.31] <Build pro4_full>.startBuild
 2011-03-09 06:48:00-0500 [Broker,0,10.1.4.31] acquireLocks(step <Build
 pro4_full>, locks [])
 2011-03-09 06:48:00-0500 [Broker,0,10.1.4.31] acquireLocks(step
 <buildbot.steps.source.SVN instance at 0xa9383ac>, locks [])
 2011-03-09 06:48:00-0500 [Broker,0,10.1.4.31]
 ShellCommand.startCommand(cmd=<RemoteCommand 'svn' at 177440364>)
 2011-03-09 06:48:00-0500 [Broker,0,10.1.4.31]   cmd.args = {'workdir':
 'build', 'patch': None, 'retry': (60, 2), 'mode': 'clobber', 'timeout':
 1200, 'svnurl':
 'https://svn.codespaces.com/cybex/symphony/Pro4Sandboxtrunk', 'revision':
 None}
 2011-03-09 06:48:00-0500 [Broker,0,10.1.4.31] <RemoteCommand 'svn' at
 177440364>: RemoteCommand.run [0]
 2011-03-09 06:48:00-0500 [Broker,0,10.1.4.31] LoggedRemoteCommand.start
 2011-03-09 06:48:54-0500 [-] SVNPoller polling
 2011-03-09 06:50:23-0500 [-] svnPoller: _process_changes last 13
 mostRecent 13
 2011-03-09 06:50:23-0500 [-] svnPoller: _process_changes 13 .. 13
 2011-03-09 06:50:23-0500 [-] SVNPoller finished polling
 2011-03-09 06:50:23-0500 [-] _finished : None
 2011-03-09 06:51:04-0500 [Broker,0,10.1.4.31] <RemoteCommand 'svn' at
 177440364> rc=1
 2011-03-09 06:51:04-0500 [-] closing log <buildbot.status.builder.LogFile
 instance at 0xa93874c>
 2011-03-09 06:51:04-0500 [-] releaseLocks(<buildbot.steps.source.SVN
 instance at 0xa9383ac>): []
 2011-03-09 06:51:04-0500 [-]  step 'svn' complete: failure
 2011-03-09 06:51:04-0500 [-]  <Build pro4_full>: build finished
 }}}

--

Comment (by dustin):

 You should look at the logs in the web status to see what went wrong - it
 could be any number of things.

-- 
Ticket URL: <http://trac.buildbot.net/ticket/1883#comment:1>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation


More information about the Commits mailing list