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 ronaldoussoren
Recipients belopolsky, flox, ixokai, l0nwlf, loewis, michael.foord, orsenthil, pitrou, r.david.murray, ronaldoussoren
Date 2010-11-16.06:55:57
SpamBayes Score 4.212862e-07
Marked as misclassified No
Message-id <>
If anything should be done the test that checks the output of id -G should be removed if we want the buildbot to keep running without problems when you change the buildbots account.

After reading the message about the new failures again I don't think this is the OSX issue I mentioned (an which is explain in painfull detail earlier in the message list): it's just that the buildbot account got changed (unintentionally) while buildbot was running.

BTW. I don't understand why adding a new account to an OSX machine adds existing accounts to a new group, I have never seen that behaviour before (on OSX).

I'm -1 on changing anything for now and do not consider this to be a bug in Python or its testset.
Date User Action Args
2010-11-16 06:55:59ronaldoussorensetrecipients: + ronaldoussoren, loewis, ixokai, belopolsky, orsenthil, pitrou, r.david.murray, michael.foord, flox, l0nwlf
2010-11-16 06:55:59ronaldoussorensetmessageid: <>
2010-11-16 06:55:57ronaldoussorenlinkissue7900 messages
2010-11-16 06:55:57ronaldoussorencreate