<div class="gmail_quote">On Fri, Sep 24, 2010 at 06:49, Antoine Pitrou <span dir="ltr"><<a href="mailto:solipsis@pitrou.net">solipsis@pitrou.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Fri, 24 Sep 2010 13:38:44 +0200<br>
"Amaury Forgeot d'Arc" <<a href="mailto:amauryfa@gmail.com">amauryfa@gmail.com</a>> wrote:<br>
> 2010/9/24 Antoine Pitrou <<a href="mailto:solipsis@pitrou.net">solipsis@pitrou.net</a>>:<br>
> ><br>
> > The getlogin test fails on many Unix buildbots, either with errno 2<br>
> > (ENOENT) or 22 (EINVAL) or "OSError: unable to determine login name":<br>
><br>
> Do these buildbots run in a Windows service, i.e. with no user logged in?<br>
<br>
</div>I don't think any of our Unix buildbots runs in our Windows service :)<br>
<br>
The diversity of errors we get is a bit disturbing: in the Linux man<br>
pages, ENOENT is mentioned as a glibc extension (“There was no<br>
corresponding entry in the utmp-file”) but EINVAL is not mentioned at<br>
all; also, returning NULL without setting errno is not a possibility in<br>
the POSIX spec.<br>
<br>
Regards<br>
<font color="#888888"><br>
Antoine.</font></blockquote><div><br></div><div>Now, it makes sense why there was no os.getlogin() test in the past. I'll disable the test for the time being.</div></div>