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

crypto/tls: TestServerHandshakeContextCancellation failure with "Socket is not connected" on js-wasm #45590

Closed
bcmills opened this issue Apr 15, 2021 · 3 comments
Closed

crypto/tls: TestServerHandshakeContextCancellation failure with "Socket is not connected" on js-wasm #45590

bcmills opened this issue Apr 15, 2021 · 3 comments
Labels
arch-wasm WebAssembly issues FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Milestone
Backlog

Comments

@bcmills
Copy link
Contributor

bcmills commented Apr 15, 2021

2021-03-19T19:59:56-3b0d288/js-wasm

--- FAIL: TestServerHandshakeContextCancellation (0.00s)
    handshake_server_test.go:1975: Unexpected server handshake error: write tcp 127.0.0.1:1->127.0.0.1:228: Socket is not connected
    handshake_server_test.go:1981: conn.Close does not error as expected when called multiple times on WASM
FAIL
FAIL	crypto/tls	8.362s

It isn't obvious to me whether this is the same underlying problem as #45299 and/or #45106 (CC @johanbrandhorst)
@bcmills bcmills added the arch-wasm WebAssembly issues label Apr 15, 2021
@bcmills bcmills added this to the Backlog milestone Apr 15, 2021
@bcmills bcmills added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Apr 15, 2021
@bcmills
Copy link
Contributor Author

bcmills commented Apr 15, 2021

Also seen on a TryBot: https://storage.googleapis.com/go-build-log/e31d7a76/js-wasm_498d5646.log

@johanbrandhorst
Copy link
Member

With #45106 resolved, hopefully it should tell us whether this is the same bug.

@bcmills bcmills added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Apr 16, 2021
@gopherbot
Copy link

Timed out in state WaitingForInfo. Closing.

(I am just a bot, though. Please speak up if this is a mistake or you have the requested information.)

@golang golang locked and limited conversation to collaborators May 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
arch-wasm WebAssembly issues FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
3 participants
@bcmills @johanbrandhorst @gopherbot