On Fri, Sep 24, 2010 at 06:49, Antoine Pitrou <solipsis at pitrou.net> wrote: > On Fri, 24 Sep 2010 13:38:44 +0200 > "Amaury Forgeot d'Arc" <amauryfa at gmail.com> wrote: > > 2010/9/24 Antoine Pitrou <solipsis at pitrou.net>: > > > > > > The getlogin test fails on many Unix buildbots, either with errno 2 > > > (ENOENT) or 22 (EINVAL) or "OSError: unable to determine login name": > > > > Do these buildbots run in a Windows service, i.e. with no user logged in? > > I don't think any of our Unix buildbots runs in our Windows service :) > > The diversity of errors we get is a bit disturbing: in the Linux man > pages, ENOENT is mentioned as a glibc extension (“There was no > corresponding entry in the utmp-file”) but EINVAL is not mentioned at > all; also, returning NULL without setting errno is not a possibility in > the POSIX spec. > > Regards > > Antoine. Now, it makes sense why there was no os.getlogin() test in the past. I'll disable the test for the time being. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20100924/5d6c251b/attachment.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4