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

crypto/tls: fails on snow leopard (tls.TestAlertForwarding Got error: received unexpected value on one of the channel) #381

Closed
gopherbot opened this issue Dec 4, 2009 · 8 comments

Comments

@gopherbot
Copy link

by f.guerrieri:

What steps will reproduce the problem?
1. ./all.bash
2. Unexpected failure
What is the expected output? What do you see instead?

cd crypto/tls && gomake test
gotest
rm -f _test/crypto/tls.a _gotest_.8
8g -o _gotest_.8 alert.go common.go handshake_client.go
handshake_messages.go handshake_server.go prf.go record_process.go
record_read.go record_write.go ca_set.go tls.go   
handshake_messages_test.go handshake_server_test.go prf_test.go
record_process_test.go record_read_test.go
rm -f _test/crypto/tls.a
gopack grc _test/crypto/tls.a _gotest_.8 
--- FAIL: tls.TestAlertForwarding
    Got error: received unexpected value on one of the channels:
script.channelClosed{channel:(chan interface { })(0x2473c0)}. Runnable
events: recv alert
FAIL
make[1]: *** [test] Error 1
make: *** [crypto/tls.test] Error 2


What is your $GOOS?  $GOARCH?

darwin 386

Which revision are you using?  (hg identify)

~/go 516 $ hg identify
29a43c7451c6 tip
@rsc
Copy link
Contributor

rsc commented Dec 10, 2009

Comment 1:

I wonder if this is related to 
http://groups.google.com/group/golang-nuts/browse_frm/thread/a5ffb666998facf5/a20043e5ad136572?
lnk=gst&q=crypto+optimizer#a20043e5ad136572
though I don't know what's going on.

Owner changed to a...@golang.org.

Status changed to Accepted.

@gopherbot
Copy link
Author

Comment 2 by f.guerrieri:

I checked against the latest hg revision and it was still failing yesterday. Don't
have the id of the revision at the moment.

@rsc
Copy link
Contributor

rsc commented Dec 16, 2009

Comment 3:

f.guerrieri: Could you please run "hg pull -u", rerun all.bash, and try again?
Ken found and fixed an optimizer bug or two in the compilers
that could have been what was causing this.
Thanks.

@rsc
Copy link
Contributor

rsc commented Dec 16, 2009

Comment 4:

Status changed to WaitingForReply.

@gopherbot
Copy link
Author

Comment 5 by f.guerrieri:

rsc: here we go
~/go 501 $ hg pull -u
pulling from https://go.googlecode.com/hg
searching for changes
adding changesets
adding manifests
adding file changes
added 47 changesets with 657 changes to 607 files
607 files updated, 0 files merged, 0 files removed, 0 files unresolved
~/go 502 $ cd src
~/go/src 503 $ ./all.bash 1> log.txt 2>&1
~/go/src 504 $ tail log.txt 
chameneosredux
--- cd ../test
fail: ken/chan.go
55,57d54
< =========== ken/chan.go
< tots=10941 totr=10941 sb=10944
< 
1 known bugs; 0 unexpected bugs; test output differs
make: *** [run] Error 1
~/go 514 $ hg identify
b0524afd0d7c tip
I attach the log. Thanks in advance!
Francesco

Attachments:

  1. log.txt.bz2 (11098 bytes)

@gopherbot
Copy link
Author

Comment 6 by MauriceGilden:

I have this same problem on 386/Linux if I set GOMAXPROCS to 2. With 1 the test 
works fine.
$ hg identify
c82a8a767ef5 tip

@gopherbot
Copy link
Author

Comment 7 by f.guerrieri:

Shadow: I have found that you can build with GOMAXPROCS set to 1, and then set it
back to 2.

@rsc
Copy link
Contributor

rsc commented Jan 18, 2010

Comment 8:

I think the optimizer fix I mentioned earlier fixed the TestAlertForwarding bug.
The ken/chan.go failure with GOMAXPROCS>1 is known, as discussed on the mailing 
list.

Status changed to Fixed.

@mikioh mikioh changed the title crypto/tls fails on snow leopard (tls.TestAlertForwarding Got error: received unexpected value on one of the channel) crypto/tls: fails on snow leopard (tls.TestAlertForwarding Got error: received unexpected value on one of the channel) Jan 14, 2015
@golang golang locked and limited conversation to collaborators Jun 24, 2016
This issue was closed.
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

2 participants