[Python-Dev] cpython (3.2): Issue #11956: Skip test_import.test_unwritable_directory on FreeBSD when run as

[Cameron Simpson]

On 08Oct2011 01:13, Michael Foord <fuzzyman at voidspace.org.uk> wrote:
| On 08/10/2011 00:19, Terry Reedy wrote:
| >On 10/7/2011 6:18 AM, Glyph wrote:
| >
| >>To sum up what I believe is now the consensus from this thread:
| >>
| >> 1. Anyone setting up a buildslave should take care to invoke the build
| >>    in an environment where an out-of-control buildbot, potentially
| >>    executing arbitrarily horrible and/or malicious code, should not
| >>    damage anything. Builders should always be isolated from valuable
| >>    resources, although the specific mechanism of isolation may differ.
| >>    A virtual machine is a good default, but may not be sufficient;
| >>    other tools for cutting of the builder from the outside world would
| >>    be chroot jails, solaris zones, etc.
| >> 2. Code runs differently as privileged vs. unprivileged users.
| >
| >My particular concern with testing as an unprivileged user comes
| >from experience with too many (commercial, post-XP) Windows
| >programs that only run correctly as admin (without an obvious good
| >reason).
| 
| It would seem that for this use case it is more important that all
| tests pass when run as a *non-admin* user.

I'm pretty sure that's what Terry meant; if these apps were tested non-admin
they wouldn't need to run as "admin (without an obvious good reason".

Cheers,
-- 
Cameron Simpson <cs at zip.com.au> DoD#743
http://www.cskk.ezoshosting.com/cs/

It is easier to optimize correct code than to correct optimized code.
- Bill Harlan