This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ixokai
Recipients belopolsky, flox, ixokai, l0nwlf, loewis, michael.foord, orsenthil, pitrou, r.david.murray, ronaldoussoren
Date 2010-11-11.21:17:44
SpamBayes Score 1.5386723e-08
Marked as misclassified No
Message-id <1289510266.56.0.641456089077.issue7900@psf.upfronthosting.co.za>
In-reply-to
Content
This test is failing again, and IIUC, largely due to the same sort of issues: http://www.python.org/dev/buildbot/all/builders/AMD64%20Leopard%203.1/builds/65

I was able to track down what exactly caused it to fail in this case on my box, though. Whatever "posix.getgroups()" ends up calling, appears to be tied to the current users login -- or at least, doesn't get updated when new groups are added to the user.

This failure happened because at some point after the buildbot was up and running, I added a new user to the machine (totally unconnected to the existing buildbot runner): this caused a new group to be added to the buildbot runner's user.

"id -G" starts returning that group immediately, but "posix.getgroups()" returns the same list as it had before. I was able to further reproduce it in Terminal, by having a console open, and compiling 3.1 there then adding a user, and running the test. It fails. Opening up a new terminal window, running the test-- and it succeeds. The original console continues to fail.
History
Date User Action Args
2010-11-11 21:17:46ixokaisetrecipients: + ixokai, loewis, ronaldoussoren, belopolsky, orsenthil, pitrou, r.david.murray, michael.foord, flox, l0nwlf
2010-11-11 21:17:46ixokaisetmessageid: <1289510266.56.0.641456089077.issue7900@psf.upfronthosting.co.za>
2010-11-11 21:17:44ixokailinkissue7900 messages
2010-11-11 21:17:44ixokaicreate