Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

x/sys/windows/svc/mgr: TestOpenLanManServer fails #11156

Closed
alexbrainman opened this issue Jun 11, 2015 · 5 comments
Closed

x/sys/windows/svc/mgr: TestOpenLanManServer fails #11156

alexbrainman opened this issue Jun 11, 2015 · 5 comments

Comments

@alexbrainman
Copy link
Member

@alexbrainman alexbrainman commented Jun 11, 2015

From our builder http://build.golang.org/log/b777dbdb4f736aafe2eacbccee3c499bf7729625

--- FAIL: TestOpenLanManServer-2 (0.00s)
mgr_test.go:23: SCM connection failed: Access is denied.
FAIL
FAIL golang.org/x/sys/windows/svc/mgr 0.043s

I don't know what the problem is.

Alex

@alexbrainman
Copy link
Member Author

@alexbrainman alexbrainman commented Jun 11, 2015

@bradfitz

@bradfitz
Copy link
Contributor

@bradfitz bradfitz commented Jun 11, 2015

I don't know either. I am not a Windows person.

Make that test t.Skip if it can't get access?
Add more logging about why it doesn't have access?

@alexbrainman
Copy link
Member Author

@alexbrainman alexbrainman commented Jun 12, 2015

"Access is denied" means the user who executes the syscall is not authorized for that operation. Who is the user? Is he an Administrator? Is he a member of Admin group?

It would be helpful, if I can debug this. Do you have a disk image that I can spin up on GCE or some other way?

I will disable the test if nothing else. I suspect I'll have to disable all tests in that package too.

Alex

@alexbrainman
Copy link
Member Author

@alexbrainman alexbrainman commented Jun 12, 2015

We cannot try-bot x/sys. Can we?

Alex

@bradfitz
Copy link
Contributor

@bradfitz bradfitz commented Jun 12, 2015

You can't share disk images on GCE (I don't think? or maybe not yet?), so you'll have to recreate your own or infer the environment from the description: https://github.com/golang/build/tree/master/env/windows I followed those instructions exactly.

You could add more logging to your failure message to say who the user is and what groups the user is in.

Trybots would work now but they're not wired up. That would actually be easy now. We should do that. (/cc @adg)

@golang golang locked and limited conversation to collaborators Jun 25, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants