On Mon, May 12, 2014 at 5:16 PM, Claudiu Popa <pcmanticore@gmail.com> wrote:
Hello!
I'm working on a patch for issue bugs.python.org/issue8579 (Add missing tests for FlushKey, LoadKey, and SaveKey in winreg). This issue requires the SeBackupPrivilege in order to use LoadKey and SaveKey. While acquiring the privilege isn't very complicated using ctypes, it fails with ERROR_NOT_ALL_ASSIGNED (1300) when the user has Administrative privileges, but it's not an Administrator, problem which can be eluded by running the script with elevated privileges. This leads me to a couple of questions:
- should a Windows test be skipped if it can't acquire a certain privilege?
Yes. Check out any of the os.symlink tests - they're currently skipped when the symlink privilege isn't held.
- If we can acquire the privilege by elevating our process, does the Windows buildbots have UAC enabled and if so, how's the notification setting configured? For instance, elevating a process will trigger a new UAC window with the message "Do you want to allow the following program from an unknown publisher to make changes to this computer?" on the recommended configuration, but this doesn't happen when the configuration is set to "Never notify".
That probably depends on how each machine is setup. If they happen to get blocked on any individual slave, we'll just have to ask the owner to change that setting. Currently there are no Windows build slaves running as administrator. I used to have one but the machine died and I never replaced it. I also said a few months ago that I would get one setup again, but that hasn't happened yet. I can get a new machine up and running but probably not until next week as I'm at a conference.