Skip to content

go build command-line-arguments: read |0: interrupted system call #349

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

Closed
tg123 opened this issue May 12, 2016 · 32 comments
Closed

go build command-line-arguments: read |0: interrupted system call #349

tg123 opened this issue May 12, 2016 · 32 comments

Comments

@tg123
Copy link
Member

tg123 commented May 12, 2016

Microsoft Windows [Version 10.0.14342]

install go from apt-get install golang

$ go version
go version go1.2.1 linux/amd64

go build
go build command-line-arguments: read |0: interrupted system call

However, it cloud work without error sometimes

@stehufntdev
Copy link
Collaborator

Thanks for reporting the issue. We investigated this locally and it is caused by missing support for restartable system calls (i.e. SA_RESTART flag).

Please give us feedback on the uservoice page so we can prioritize.

@mvadu
Copy link

mvadu commented May 22, 2016

@stehufntdev the repo readme says "This repo is for the reporting of issues found within and when using Bash on Ubuntu on Windows", and you are asking us to go to UserVoice? Then what is the point of reporting it here?

@aseering
Copy link
Contributor

aseering commented May 22, 2016

@mvadu -- Github is good at capturing and discussing technical information about a bug or feature request. But there are many (I'm guessing at least hundreds if not thousands?) of people reporting bugs or requesting features or (etc) against WSL. I've seen bug trackers where bugs for popular issues get tons of "me too!"'s, and it's a real pain to read through all of those comments to figure out what the actual bug is, find the latest updates from the people who are actually debugging it, etc. So the important bugs actually become more annoying to fix.

I think Microsoft is trying to differentiate between technical issues and use cases. Your report is both -- "go build is an important command for developing Go software" is a use case; "go build doesn't work because of lack of SA_RESTART support" is a technical issue. So it's useful to have it in both places.

@mvadu
Copy link

mvadu commented May 23, 2016

@aseering I did create a new user voice topic for this as well.

@simonbuchan
Copy link

Also happens with github's hub command (written in go). Since that's recommended to be aliased to git, this can hit pretty often!

@RobWC
Copy link

RobWC commented Aug 2, 2016

+1

@technowar
Copy link

technowar commented Oct 11, 2016

@simonbuchan, if it annoys you, use brew or Ruby's version. The latter isn't recommended.

Anyways, any updates on this?

@tg123
Copy link
Member Author

tg123 commented Oct 11, 2016

fixed in 14905
https://msdn.microsoft.com/en-us/commandline/wsl/release_notes

works fine now

@retorquere
Copy link

How do I get 14905 on my system?

@stehufntdev
Copy link
Collaborator

14905 is a Windows insider build, to get that on your system you need to enroll the machine in the Windows insider program.

@sleaze
Copy link

sleaze commented Oct 24, 2016

What if we don't want to opt into full telemetry? :s

@MikeCook9994
Copy link

You don't get windows insider. Windows insider isn't for you to get builds and fixes early. It's to get information about their new builds.

@aseering
Copy link
Contributor

@MikeCook9994 -- could you provide a reference for that statement? I install Insider builds from here on a regular basis: https://insider.windows.com/

@cheynewallace
Copy link

Is there any indication as to when this 14905 build will be generally available? I am trying to move some of my build operations from Mac to Windows and this has completely blocked me as I cannot go build from bash. I'd prefer to not have to enroll in some insiders program and just use the stable release.

@benhillis
Copy link
Member

The Windows 10 Creators update which is due early 2017.

@ausrasul
Copy link

ausrasul commented Dec 28, 2016

I got this problem right after I modified files in Bash FROM WIndows C:/Users/myself/AppData/loca/lxss/

I cloned my project again on another directory and now it works. Will edit files via ssh from now on.

Update: Forget what I wrote, I got the error again. only with Golang "compile" tool.

@ausrasul
Copy link

@cheynewallace I'm running Stable, having the same problem here.

@robbiev
Copy link

robbiev commented Jan 29, 2017

I read somewhere that go 1.6.x might work and indeed, 1.6.4 does work for me. More recent versions of go don't work.

@Zanndorin
Copy link

I can confirm that go 1.6.4 works

thank you @robbiev

@sunilmut
Copy link
Member

sunilmut commented Mar 1, 2017

@robbiev - Thanks for the post. Can you please provide more details on which version of go is not working and detailed repro steps?

@stehufntdev
Copy link
Collaborator

@mrbeskin can you please let us know which Windows build you are running? There is a known issue preventing go from working in the Anniversary update which has been fixed for insider builds.

@mrbeskin
Copy link

@stehufntdev Sorry, deleted my comment before I saw there was a reply . . . I realized I was on the Anniversary update. I am working on getting my hands on the latest available build and I will test there. Thank you for your reply.

@stehufntdev
Copy link
Collaborator

No worries, thanks for the confirmation! Please let us know if you see any issues for insider builds.

@cweeks12
Copy link

Is there any indication of when this build is going to be available generally? I just ran into this issue in my Go development

@benhillis
Copy link
Member

@cweeks12 - Creator's update is due soon. I don't have an exact date but I think April or early May.

@fraklo
Copy link

fraklo commented Mar 22, 2017

Not sure if it's been noted, but I get the same issue when trying to run
go run test.go
if however I run
go run ./*
or even go up a directory and run
go run test_dir/*
The file runs.

@JamieSinn
Copy link

This issue is still persisting.

@sunilmut
Copy link
Member

@fraklo and @JamieSinn - I tried this simple example https://gobyexample.com/reading-files and it worked fine for me. I was able to run the file using the command go run test.go. I am running go version 1.6.2. This was on Insiders build 16215. If the issue persists for you, please include the Windows build that you are running (output of the ver command) and an strace strace -o <strace_file> -ff <failing_cmd>

$go version
go version go1.6.2 linux/amd64

@JamieSinn
Copy link

JamieSinn commented Jun 13, 2017

I am using go 1.8, I have not used an insider's build.
Will grab stack traces soon.

@sunilmut
Copy link
Member

@JamieSinn - Ok, thanks. Please also post your Windows version (using the ver CMD) and full repro steps.

@kanonji
Copy link

kanonji commented Aug 21, 2017

I tried https://gobyexample.com/reading-files and not worked.

$ go run reading-files.go
go build command-line-arguments: /home/kanonji/local/stock/go1.8.3.linux-amd64/pkg/tool/linux_amd64/compile: read |0: interrupted system call
$ cat go-run-reading-files-go.sh
#!/bin/sh
go run reading-files.go

$ strace -ff -o straced/go-run-reading-files-go ./go-run-reading-files-go.sh
go build command-line-arguments: /home/kanonji/local/stock/go1.8.3.linux-amd64/pkg/tool/linux_amd64/link: read |0: interrupted system call

strace generates 20 files. Do you need all files or maybe only last one?

$ go version
go version go1.8.3 linux/amd64
>ver

Microsoft Windows [Version 10.0.14393]

@therealkenc
Copy link

The OP here was related to restartable system calls and was addressed in 14905 and by extension Creators Update 15063.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests