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

Jump to bottom

misc/cgo/testcarchive: Go 1.7 test failure: got signal: broken pipe; expected SIGSEGV #19905

Closed
EndlessIdea opened this issue Apr 10, 2017 · 5 comments
Closed

misc/cgo/testcarchive: Go 1.7 test failure: got signal: broken pipe; expected SIGSEGV #19905

EndlessIdea opened this issue Apr 10, 2017 · 5 comments
Labels
FrozenDueToAge WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Milestone
Unplanned

Comments

@EndlessIdea
Copy link

Please answer these questions before submitting your issue. Thanks!

What version of Go are you using (go version)?

go 1.7.4

What operating system and processor architecture are you using (go env)?

linux

What did you do?

I downloaded go1.8, tar zxvf it, then sh src/all.bash. But I didn't install successfully.

../misc/cgo/testgodefs
../misc/cgo/testso
../misc/cgo/testsovar
../misc/cgo/testcarchive

--- FAIL: TestSignalForwarding (0.79s)
carchive_test.go:265:
carchive_test.go:266: got signal: broken pipe; expected SIGSEGV
FAIL
2017/04/10 16:19:13 Failed: exit status 1

What did you expect to see?

I expect to see install succefully.

What did you see instead?

Fail
@bradfitz
Copy link
Contributor

Can you try Go 1.8? We no longer maintain Go 1.7, except for critical/security issues.

@bradfitz bradfitz added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Apr 10, 2017
@bradfitz bradfitz changed the title carchive_test.go:266: got signal: broken pipe; expected SIGSEGV misc/cgo/testcarchive: Go 1.7 test failure: got signal: broken pipe; expected SIGSEGV Apr 10, 2017
@bradfitz bradfitz added this to the Unplanned milestone Apr 10, 2017
@ianlancetaylor
Copy link
Contributor

Don't forget to tell us what type of processor you are using. It matters.

@EndlessIdea
Copy link
Author

@bradfitz Sorry, I can't use Go 1.8, because what I was trying to do is to update Go 1.7 to Go 1.8. I came to this problem when I was running src/all.bash to update Go version to 1.8.

@EndlessIdea
Copy link
Author

@ianlancetaylor OK. Here's my processor info.
model name : Intel Xeon E312xx (Sandy Bridge)
stepping : 1
cpu MHz : 2094.950
cache size : 4096 KB

@ALTree
Copy link
Member

ALTree commented Sep 22, 2018 •
edited

Go1.7 is no longer maintained and we never received other reports of this test failure, so I think it's safe to assume that this is no longer a problem. Closing here.

@ALTree ALTree closed this as completed Sep 22, 2018
@golang golang locked and limited conversation to collaborators Sep 22, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Projects
None yet
Milestone
Unplanned
Development

No branches or pull requests
5 participants
@bradfitz @EndlessIdea @ianlancetaylor @ALTree @gopherbot