Ronald Oussoren <[email protected]> added the comment:
Please explain how the failure can be reproduced.
I've done some testing on my machine using Apple's copy of python 2.6.1 (on OSX
10.6), which has the same getgroups implementation as the current heads of the
active branches.
>>> os.getgroups()
[20, 402, 204, 61, 12, 401]
>>> os.system("id -G")
20 402 204 61 12 401
0
(Now open the Accounts preference pane and add a new user)
>>> os.getgroups()
[20, 403, 402, 204, 61, 12, 401]
>>> os.system("id -G")
20 403 402 204 61 12 401
0
Note how the result of both os.getgroups and id -G changes, which should mean
that tests shouldn't fail unless you happened to add a new account in the
split-second between the "calls" to os.getgroups and "id -G" in a testrun.
Was the buildbot started using launchd (the recipe at
<http://buildbot.net/trac/wiki/UsingLaunchd> seems correct)? If not, how is it
started?
----------
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue7900>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
