ssh: skip testHandshakeErrorHandlingN on js/wasm

The wasm runtime cannot schedule a GC run on tight loops.
Therefore it runs out of memory if such a loop allocates memory.

Skip such a test for now.

Updates golang/go#32840

Change-Id: I922b6e02710915776d2820573fd1584a5941185b
Reviewed-on: https://go-review.googlesource.com/c/crypto/+/184397
Run-TryBot: Agniva De Sarker <agniva.quicksilver@gmail.com>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Han-Wen Nienhuys <hanwen@google.com>
This commit is contained in:
Agniva De Sarker 2019-07-01 14:29:26 +05:30 коммит произвёл Agniva De Sarker
Родитель cc06ce4a13
Коммит 4def268fd1
1 изменённых файлов: 3 добавлений и 0 удалений

Просмотреть файл

@ -421,6 +421,9 @@ func TestHandshakeErrorHandlingWriteCoupled(t *testing.T) {
// handshakeTransport deadlocks, the go runtime will detect it and
// panic.
func testHandshakeErrorHandlingN(t *testing.T, readLimit, writeLimit int, coupled bool) {
if runtime.GOOS == "js" && runtime.GOARCH == "wasm" {
t.Skip("skipping on js/wasm; see golang.org/issue/32840")
}
msg := Marshal(&serviceRequestMsg{strings.Repeat("x", int(minRekeyThreshold)/4)})
a, b := memPipe()