Ticket #508 (closed defect: duplicate)

Opened 4 years ago

Last modified 4 years ago

try command is failing

Reported by: ipv6guru Owned by:
Priority: major Milestone: undecided
Version: 0.7.10 Keywords: sourceforge 1796252
Cc:

Description

Hello List,

I am evaluating buildbot and face some trouble: can't get the try command to work:

command used: tst.user$ buildbot try --connect='pb' --master='192.168.191.131:8031' --username='tst.user' --passwd='blah' --builder='buildbot_app' --vc='cvs' --wait using 'pb' connect method job created job has been delivered contacting the status port at hinkelstein.bc-int.net:8031 Unhandled error in Deferred: Traceback from remote host -- Traceback unavailable All Builds Complete buildbot_app: failure (failed cvs)

log output: 2007/09/17 14:23 +0200 [Broker,0,192.168.191.131] <buildbot.scheduler.Try_Userpass instance at 0xb79cd58c> got connection from user tst.user 2007/09/17 14:23 +0200 [Broker,0,192.168.191.131] user tst.user requesting build on builders buildbot_app? 2007/09/17 14:23 +0200 [Broker,0,192.168.191.131] maybeStartBuild <Builder 'buildbot_app' at -1216108148>: [<buildbot.pro cess.base.BuildRequest? instance at 0xb776a9ec>] [<buildbot.process.builder.SlaveBuilder? instance at 0xb776060c>] 2007/09/17 14:23 +0200 [Broker,0,192.168.191.131] starting build <Build buildbot_app>.. pinging the slave 2007/09/17 14:23 +0200 [Broker,0,192.168.191.131] sending ping 2007/09/17 14:23 +0200 [Broker,0,192.168.191.131] ping finished: success 2007/09/17 14:23 +0200 [Broker,0,192.168.191.131] <Build buildbot_app>.startBuild 2007/09/17 14:23 +0200 [Broker,0,192.168.191.131] acquireLocks(step <Build buildbot_app>, locks []) 2007/09/17 14:23 +0200 [Broker,0,192.168.191.131] acquireLocks(step <buildbot.steps.trigger.TriggerScheduler? instance at 0xb776a48c>, locks []) 2007/09/17 14:23 +0200 [Broker,0,192.168.191.131] maybeStartBuild <Builder 'buildbot_package' at -1214666932>: [<buildbot .process.base.BuildRequest? instance at 0xb775d96c>] [<buildbot.process.builder.SlaveBuilder? instance at 0xb77602ec>] 2007/09/17 14:23 +0200 [Broker,0,192.168.191.131] starting build <Build buildbot_package>.. pinging the slave 2007/09/17 14:23 +0200 [Broker,0,192.168.191.131] sending ping 2007/09/17 14:23 +0200 [Broker,0,192.168.191.131] ping finished: success 2007/09/17 14:23 +0200 [Broker,0,192.168.191.131] <Build buildbot_package>.startBuild 2007/09/17 14:23 +0200 [Broker,0,192.168.191.131] acquireLocks(step <Build buildbot_package>, locks []) 2007/09/17 14:23 +0200 [Broker,0,192.168.191.131] acquireLocks(step <buildbot.steps.source.CVS instance at 0xb776f90c>, l ocks []) 2007/09/17 14:23 +0200 [Broker,0,192.168.191.131] ShellCommand?.startCommand(cmd=%s) (<RemoteCommand? 'cvs' at -1217018388> ,) 2007/09/17 14:23 +0200 [Broker,0,192.168.191.131] <RemoteCommand? 'cvs' at -1217018388>: RemoteCommand?.run [0] 2007/09/17 14:23 +0200 [Broker,0,192.168.191.131] LoggedRemoteCommand?.start 2007/09/17 14:23 +0200 [Broker,1,192.168.191.131] Peer will receive following PB traceback: 2007/09/17 14:23 +0200 [Broker,1,192.168.191.131] Unhandled Error Traceback (most recent call last): Failure: twisted.cred.error.UnauthorizedLogin?:

2007/09/17 14:23 +0200 [Broker,0,192.168.191.131] <RemoteCommand? 'cvs' at -1217018388> rc=1 2007/09/17 14:23 +0200 [-] closing log <buildbot.status.builder.LogFile? instance at 0xb775c22c>

AFAIK everythis is set up correctly according to the buildbot manual: PB approach used.

master.cfg contains a Try_Userpass scheduler: s = Try_Userpass("try2", ["buildbot_app", "buildbot_package", "buildbot_subpack"], port=8031, userpass=[('tst.user','blah'), ] ) cschedulers?.append(s)

does anybody have an idea why this login error occurs? I can force build the test project using the same user.

Thanks, Paul Submitted: paul_buchmeier ( paul_buchmeier ) - 2007-09-17 22:35

Change History

comment:1 Changed 4 years ago by ipv6guru

Moved from sourceforge

comment:2 Changed 4 years ago by dustin

  • Status changed from new to closed
  • Resolution set to duplicate

try handling needs an overhaul - #492

Note: See TracTickets for help on using tickets.