Fix three Windows base_unittests to not require admin

Fix three Windows base_unittests to not require admin

These three base_unittests tests fail when run as non-admin on Windows
if %temp% is set to a non-standard location such as d:\src\temp:

- FileTest.GetInfoForDirectory
- FileUtilTest.FileEnumeratorTest
- FileUtilTest.NormalizeFilePathReparsePoints

They all fail because the default user doesn't have enough permissions
to open the directories with FILE_ALL_ACCESS.

Asking for fewer permissions allows the tests to pass regardless of
user-type and %temp% location.

R=rvargas@chromium.org
BUG=533018
Committed: https://crrev.com/35b35d85da7746865bc66f3dee35487567e0a356
Cr-Commit-Position: refs/heads/master@{#349485}

[brucedawson, 2015-09-17 17:50:13]

If there is a fundamental reason why these tests are *supposed* to require admin
I could fix them differently (detect admin and warn) but it seems better to have
the tests succeed as non-admin.

My command prompts are always non-elevated so I always hit this.

[rvargas (doing something else), 2015-09-17 20:01:52]

On 2015/09/17 17:50:13, brucedawson wrote:
> If there is a fundamental reason why these tests are *supposed* to require
admin
> I could fix them differently (detect admin and warn) but it seems better to
have
> the tests succeed as non-admin.
> 
> My command prompts are always non-elevated so I always hit this.

I always run as non-admin to start with and everything works fine :P

The critical distinction IMO is that the test location (where the test is going
to try stuff, aka temp) is non standard in your case, and it doesn't grant the
text executable enough privileges to test what it wants. From that point of view
I'd say there's nothing to fix.

On the other hand, I see no reason to ask for something more than GENERIC_foo in
this case, so as long as everything works, I'm fine with the change.

lgtm.

[brucedawson, 2015-09-17 20:08:44]

Yep, I discovered after uploading this that the default temp location works
fine. I'll update the CL description to reflect that.

Note that the setup instructions (IIRC) recommend pointing temp at a directory
inside of \src in order to benefit from bit9 exemptions, so the non-standard
location is probably pretty common at Google.

[brucedawson, 2015-09-17 20:10:44]

The CQ bit was checked by brucedawson@chromium.org

[commit-bot: I haz the power, 2015-09-17 20:11:13]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1348533003/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1348533003/1

[rvargas (doing something else), 2015-09-17 20:22:32]

On 2015/09/17 20:08:44, brucedawson wrote:
> Yep, I discovered after uploading this that the default temp location works
> fine. I'll update the CL description to reflect that.
> 
> Note that the setup instructions (IIRC) recommend pointing temp at a directory
> inside of \src in order to benefit from bit9 exemptions, so the non-standard
> location is probably pretty common at Google.

hmmm. Interesting. I hope those instructions are not public.

[commit-bot: I haz the power, 2015-09-17 20:31:06]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-09-17 20:31:46]

Patchset 1 (id:??) landed as
https://crrev.com/35b35d85da7746865bc66f3dee35487567e0a356
Cr-Commit-Position: refs/heads/master@{#349485}