selftest prompts for ssh password ??

[Martin Pool]

2009/6/23 Maritza Mendez <martitzam at gmail.com>:
>
> I have just taken the 1.16 PPA packages for jaunty and started selftest,
> with stdout redirected to a file.
>
> As usual for me, the first stall occurs at
>
> test_http.TestActivity.test_get(urllib,https,HTTP/1.0)
>
> That much is reproducible.
>
> What is not reproducible is that on stderr (still attached to the console) I
> got this:
>
> SSH: bzr jim at bar.org password: SSH: bzr jim at bar.org password:
>
> Several attempts to reproduce this prompt under various circumstances
> (stdout redirected or not, stderr redirected or not) have all failed.
>
> Digging into test_config.py suggests that bzr is waiting for an interactive
> response like 'jimpass'
>
> But as I say I have not been able to repeat this...
>
> I do notice some advisements that pycurl cannot prompt, but as you can see
> this error appears to be related to urllib -- not pycurl.
>
> I say "appears" because I am assuming (without proof) that stdout and stdin
> are in sync, and there's really no good reason to believe that.  So all I
> can really say is "At a time when selftest has hung -- as confirmed by
> strace -- the last messages flushed to stdout and stderr are such-and-such."
>
> Is selftest really prompting me to enter a password?  And if so, why have I
> seen it only once in numerous selftest runs or test_http?

Well, it certainly seems like it is prompting you for it, but it's not
meant to.  The test suite is supposed to be (and is, when I run it)
entirely non-interactive and automated.

If this is coming from test_config it looks like it's just asking the
configuration file object for the right password.  In a brief look it
does not seem like that code should be asking the user for the
password.  It's possible that what you saw was echoed to a trace file
during the test and bzr printed it out when a test failed.

If you run just 'bzr selftest test_http' does that fail?

-- 
Martin <http://launchpad.net/~mbp/>